Fix: static datasource ids#3
Open
0hlov3 wants to merge 2 commits into
Open
Conversation
This fixes a Problem, that the id of the Datasource is unknown, when importing the Dashboard Changelog: fixed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove hardcoded Prometheus datasource UIDs from dashboard JSON
Why
The dashboard JSON currently hardcodes Prometheus datasource uid/id values. These values differ between Grafana instances and orgs, which often causes an “unknown datasource uid” / “data source not found” error during import. When a user has only one Prometheus datasource (or a default Prometheus datasource set), Grafana can resolve it automatically during import, as long as the dashboard doesn’t pin a specific UID.
What changed