This PR moves the health check to backend only leaving in the frontend
the functionality to test the dbconnector datasource.
Leaving the `dbconnector.testDataSource` should be fine since the
datasource types we allow for db connection with Zabbix already are
backend datasources, and so their health requests would go through the
backend.
Verified:
Clicking test and seeing a `health` request go out.
IMPORTANT: While testing this in the UI, I found a bug with the config
editor - whenever a change is made in the UI and tested, the changes
don't take effect (i.e. disabling trends, keeps `trends` set to `true`,
enabling db connection keep `dbConnectionEnabled` set to `false` and so
on.). Created a separate
[issue](https://github.com/orgs/grafana/projects/457/views/40?pane=issue&itemId=3627315751&issue=grafana%7Coss-big-tent-squad%7C132)
to fix this
Fixes https://github.com/grafana/oss-big-tent-squad/issues/124
Fixes https://github.com/grafana/grafana-zabbix/issues/2004
* Use data frames for numeric data
* Use data frames for text data
* Use data frames for IT services
* fix multiple series
* Convert to the wide format if possible
* Fix table format for text data
* Add refId to the data frames
* Align time series from Zabbix API
* Fill gaps with nulls
* Fix moving average functions
* Option for disabling data alignment
* remove unused logging
* Add labels to data frames
* Detect units
* Set min and max for if percent unit used
* Use value mapping from Zabbix
* Rename unitConverter -> convertZabbixUnit
* More units
* Add missing points in front of each series
* Fix handling table data
* fix db connector data frames handling
* fix it services data frames handling
* Detect all known grafana units
* Chore: remove unused logging
* Fix problems format
* Debug logging: show original units
* Add global option for disabling data alignment
* Add tooltip for the disableDataAlignment feature
* Add note about query options
* Functions for aligning timeseries on the backend