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
While exporting boards for external use it generated data source UID variable e.g. "$DS_PROMETHEUS". It is only useful when you have only one other environment. In my case I have three different environments and using helm charts to provision boards. In other two environment it throws error "$DS_PROMETHEUS not found" because though the data source is same e.g. prometheus UID is different.
What did you expect to happen?
It should some how auto detect the DS UID and should set it in background.
Did this work before?
No
How do we reproduce it?
In my case I have three different environments and using helm charts to provision boards. In other two environment it throws error "$DS_PROMETHEUS not found"
Is the bug inside a dashboard panel?
No
Environment (with versions)?
Grafana: 10.2.2
OS: Windows
Browser: Chrome
Grafana platform?
Kubernetes
Datasource(s)?
Prometheus and Loki
The text was updated successfully, but these errors were encountered:
Thank you for submitting the issue, tonypowa! To help us better understand and address your concern about the data source UID variable during export, could you please provide the following additional information:
Error logs or screenshots where '$DS_PROMETHEUS not found' is being shown
To reproduce the issue more effectively, it would also be valuable if you could provide a minimal example of a dashboard definition (in JSON) that is failing to import correctly due to the UID issue.
tonypowa
added
the
needs more info
Issue needs more information, like query results, dashboard or panel json, grafana version etc
label
Mar 5, 2024
What happened?
While exporting boards for external use it generated data source UID variable e.g. "$DS_PROMETHEUS". It is only useful when you have only one other environment. In my case I have three different environments and using helm charts to provision boards. In other two environment it throws error "$DS_PROMETHEUS not found" because though the data source is same e.g. prometheus UID is different.
What did you expect to happen?
It should some how auto detect the DS UID and should set it in background.
Did this work before?
No
How do we reproduce it?
Is the bug inside a dashboard panel?
No
Environment (with versions)?
Grafana: 10.2.2
OS: Windows
Browser: Chrome
Grafana platform?
Kubernetes
Datasource(s)?
Prometheus and Loki
The text was updated successfully, but these errors were encountered: