-
Notifications
You must be signed in to change notification settings - Fork 462
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
Direct DB connection - No data in Grafana 8.0 #1221
Comments
So should we simply disable "Direct DB connection" ? |
If it's work for you, you can do it. But understand that without Direct DB you can have some problem with Zabbix API query limits that just throws you a 500 error if you request too much from it. |
Well I have some bigger instance where this could be a problem (and I can not test it at the moment). Thing is I do not understand what this means (do you have any pointer to grafana 8.0 documentation/changes?):
So I don't see what alternative to not load the Zabbix API from grafana do we have (of course I can create a secondary API server and even a replicated DB if that's the option). |
@fauust I mean with the backend load for the backend will be reduced (but not so much as with direct db connection). Also, implementing direct db connection on the backend is tricky since I cannot use existing data source (maybe, I can, but I have to investigate). So my tip:
|
Great, don't hesitate to ping me if you need help in testing. |
Same problem here. :/ |
Same problem here |
I have the same problem "no data" |
@jcoliveira-dotcom do not use for now the DB connection. |
+1 |
Closed by #1256 |
Describe the bug
No data returned for queries when Direct DB connection enabled. This bug appears in Grafana 8.0.
Probably, something was changed in the SQL data sources response format, because SQL query copied from panel inspector returns data as expected.
Not sure does it make sense to fix it since queries are moving to the backend and there's no ability to use SQL data sources for querying data anymore. Maybe it will be possible in future, but backend queries solve most of problems that Direct DB connection is trying to address.
Software versions
The text was updated successfully, but these errors were encountered: