-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[grafana] cannot import a dashboard with multiple datasources from grafana.com #313
Comments
For example the Loki quick search dashboard cannot be imported correctly: https://grafana.com/grafana/dashboards/12019 |
Any updates on this? |
Did anyone found a solution for this problem? |
It is not clear how one should be importing any of the dashboards that have multiple data sources. Probably there are many more dashboards that have more than one data source. In the helm chart values we can provide only one data source, e.g:
This bug makes many dashboards incompatible with projects that use grafana chart as a dependency (kube-prometheus-stack in my case). It is very strange that issue like this (which was reported more than a year ago) still has not attracted any attention from maintainers and there are very few people interested in it... probably nobody uses grafana in combination with Loki... |
Fix grafana#313 Signed-off-by: Julien Francoz <julien-github@francoz.net>
Fix grafana#313 Signed-off-by: Julien Francoz <julien-github@francoz.net> Signed-off-by: paolopiaggio <paolo.piaggesi@gmail.com>
The following code is the section of the bash script that downloads a dashboard from Grafana:
The sed command replaces ALL datasources with the single datasource provided in values, if present.
Expected behaviour
We should be able to specify multiple datasources in the chart values and replace each datasource with the right datasource.
If the dashboard was exported with the "external" checkbox enabled, then we sould be able to replace the datasource based on the variable name (e.g, replace "${DS_PROMETHEUS}" by the actual datasource name).
The text was updated successfully, but these errors were encountered: