You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the case the query result might not be complete for various reasons, response from LogScale query will include a "warnings{}" section as part of meta data in the payload, e.g.: return items larger than maximum limit, query over memory state limit etc.
These are reported in LogScale UI so user's aware the result might be incomplete, however, currently the Grafana LogScale datasource plugin does not report this back to Grafana so user's unaware of it and potentially will be looking at incomplete/incorrect data without knowing it.
Can an indicator be added to Grafana dashboard so user's aware of the warning returned from query reponse?
What you expected to happen:
User should be aware if backend report back the query result with warning.
How to reproduce it (as minimally and precisely as possible):
Screenshots
Anything else we need to know?:
Environment:
Grafana version:
Plugin version:
OS Grafana is installed on:
User OS & Browser:
Others:
The text was updated successfully, but these errors were encountered:
What happened:
In the case the query result might not be complete for various reasons, response from LogScale query will include a "warnings{}" section as part of meta data in the payload, e.g.: return items larger than maximum limit, query over memory state limit etc.
These are reported in LogScale UI so user's aware the result might be incomplete, however, currently the Grafana LogScale datasource plugin does not report this back to Grafana so user's unaware of it and potentially will be looking at incomplete/incorrect data without knowing it.
Can an indicator be added to Grafana dashboard so user's aware of the warning returned from query reponse?
What you expected to happen:
User should be aware if backend report back the query result with warning.
How to reproduce it (as minimally and precisely as possible):
Screenshots
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: