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
I just completed a fresh install of the latest tobs v0.9.0. When I select the Kubernetes Cluster Monitoring or Kubernetes Hardware Monitoring dashboards in Grafana, I get the following errors and the dashboard does not display data.
Templating: Failed to ugprade legacy queries Datasource Prometheus was not found
Templating[Node]: Error updating options: Datasource Prometheus was not found
Templating[Namespace]: Error updating options: Datasource Prometheus was not found
Templating[Deployment]: Error updating options: Datasource Prometheus was not found
So far, all of the other dashboards work and display data. If the above dashboards are intended for use, maybe their datasource needs to be changed to Promscale-PromQL? I saw the same issue in v0.8.0
I do have my Grafana manually set to a LoadBalancer, it would be nice if this was an option in values.yaml
Thanks for the hard work on this!
The text was updated successfully, but these errors were encountered:
Hello,
I just completed a fresh install of the latest tobs v0.9.0. When I select the Kubernetes Cluster Monitoring or Kubernetes Hardware Monitoring dashboards in Grafana, I get the following errors and the dashboard does not display data.
Templating: Failed to ugprade legacy queries Datasource Prometheus was not found
Templating[Node]: Error updating options: Datasource Prometheus was not found
Templating[Namespace]: Error updating options: Datasource Prometheus was not found
Templating[Deployment]: Error updating options: Datasource Prometheus was not found
So far, all of the other dashboards work and display data. If the above dashboards are intended for use, maybe their datasource needs to be changed to Promscale-PromQL? I saw the same issue in v0.8.0
I do have my Grafana manually set to a LoadBalancer, it would be nice if this was an option in values.yaml
Thanks for the hard work on this!
The text was updated successfully, but these errors were encountered: