Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report warning field returned from LogScale query response #317

Open
fyang13 opened this issue May 9, 2024 · 0 comments
Open

Report warning field returned from LogScale query response #317

fyang13 opened this issue May 9, 2024 · 0 comments
Labels

Comments

@fyang13
Copy link

fyang13 commented May 9, 2024

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:

  • Grafana version:
  • Plugin version:
  • OS Grafana is installed on:
  • User OS & Browser:
  • Others:
@fyang13 fyang13 added datasource/Falcon LogScale type/bug Something isn't working labels May 9, 2024
@alyssabull alyssabull added enhancement New feature or request and removed type/bug Something isn't working labels May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Feature Requests
Development

No branches or pull requests

2 participants