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
Our data sources are named "env1 Prometheus", "env2 Prometheus", "envN Prometheus" because we also have "env1 Loki", "env2 Loki", etc and the data source cannot have the same name, even if they are of different types.
In our dashboards, we have a environment data source variable that selects all data sources of a given type.
The variable shows these suffixes that are not really part of the environment name. We would like to show only the proper environment name to reduce user confusion (e.g. "env1" instead of "env1 Prometheus"). Some users are very non-technical and get confused with names like data sources, Prometheus, Loki, etc.
What would you like to be added:
By supporting regular expression groups, it would be possible to display the extracted values.
There needs to be a way to template the display value while still retaining the actual value, so the correct data source is used.
Why is this needed:
Our data sources are named "env1 Prometheus", "env2 Prometheus", "envN Prometheus" because we also have "env1 Loki", "env2 Loki", etc and the data source cannot have the same name, even if they are of different types.
In our dashboards, we have a
environment
data source variable that selects all data sources of a given type.The variable shows these suffixes that are not really part of the environment name. We would like to show only the proper environment name to reduce user confusion (e.g. "env1" instead of "env1 Prometheus"). Some users are very non-technical and get confused with names like data sources, Prometheus, Loki, etc.
What would you like to be added:
By supporting regular expression groups, it would be possible to display the extracted values.
There needs to be a way to template the display value while still retaining the actual value, so the correct data source is used.
This is similar to #1032 but not quite.
Who is this feature for?
Grafana administrators and dashboard editors.
The text was updated successfully, but these errors were encountered: