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
Why is this needed:
Having template variables for the dashboard UID, panel ID and template index would accomplish at least two things:
Be able to pass fine-grained information about the source of the query to the datasource, for example by using an SQL comment. This will make it possible to quickly trace back problematic queries to the originating panel or template variable.
Make it possible to pass enough context in data links to be able to refer back to the exact panel where the query was coming from
What would you like to be added:
3 template variables: $__dashboard_uid - The UID of the current dashboard $__panel_id - The panel ID of the current panel (only for queries in panels) $__template_idx - The index of the template variable (only for template variable queries)
Who is this feature for?
Advanced users with large dashboards and datasource developers who want to include fine-grained information of Grafana usage into the datasource's query log. Possibly others as well?
The text was updated successfully, but these errors were encountered:
oplehto
changed the title
Template variables for dashboard UID, panel ID and template Index
Feature request: Template variables for dashboard UID, panel ID and template Index
May 14, 2024
Why is this needed:
Having template variables for the dashboard UID, panel ID and template index would accomplish at least two things:
What would you like to be added:
3 template variables:
$__dashboard_uid
- The UID of the current dashboard$__panel_id
- The panel ID of the current panel (only for queries in panels)$__template_idx
- The index of the template variable (only for template variable queries)Who is this feature for?
Advanced users with large dashboards and datasource developers who want to include fine-grained information of Grafana usage into the datasource's query log. Possibly others as well?
The text was updated successfully, but these errors were encountered: