grafana / grafana-zabbix

Zabbix plugin for Grafana dashboard
http://play.grafana-zabbix.org
Apache License 2.0
2.08k stars 458 forks source link

Failing to switch from postgres to influx direct connection #783

Open anthonysomerset opened 5 years ago

anthonysomerset commented 5 years ago

Describe the bug I have been using Postgres DB for Zabbix and the grafana plugin (works well) - we are migrating to InfluxDB for the longer term storage, when i attempt to switch the zabbix plugin datasource to use influx i get a failed to get metric error in the gui and existing dashboards can't read any data. the influx datasource on its own is indeed working and i can manually pull metrics out just fine. When we enabled Influx on a previous version of the plugin it worked

Expected behavior The data source should save and test correctly and data should return in dashboard panels

Screenshots Screenshot 2019-08-16 06 14 07 Screenshot 2019-08-16 06 14 24

Network data Grafana Log: t=2019-08-16T04:09:23+0000 lvl=eror msg="Metric request error" logger=context userId=2 orgId=1 uname=Anthony.Somerset@liquidtelecom.com error="type assertion to string failed"

Software versions

Grafana Zabbix Grafana-Zabbix Plugin
6.3.3 4.2.5 3.10.4
anthonysomerset commented 5 years ago

I've done some debugging further - it would seem that the direct db connection is perhaps not being saved properly in the Database - once i manually updated the DB table (like i did for #731) it actually saved and worked

alexanderzobnin commented 4 years ago

Hi! Can you confirm this happens in 3.11 as well?

anthonysomerset commented 3 years ago

its happening to me still in most current release

doesn't matter if i am switching from Influx to postgres or the reverse - the json_data field in the grafana DB does not get updated properly

specifically dbConnectionDatasourceName does not get updated - the dbConnectionDatasourceId field does get updated though

github-actions[bot] commented 3 months ago

This issue has been automatically marked as stale because it has not had activity in the last 2 years. It will be closed in 60 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions!