Grafana 13.3 Adds Shared Dashboard Variables and Notebooks

MMS Founder
MMS • Mark Silvester
Article originally posted on InfoQ. Visit InfoQ
image

Grafana Labs has released Grafana 13.3 with cross-dashboard variables that let teams manage shared dashboard controls in one place. The release also introduces Notebooks for collecting panels and investigation notes in a document that colleagues can share.

The release announcement describes cross-dashboard variables as a public preview across all Grafana editions. Teams can define a variable once and use it in multiple dashboards, avoiding separate configurations for a selector such as an environment or a region. Grafana says managing those copies separately can lead to configuration drift.

Cross-dashboard variables address a longstanding user request. In a 2021 GitHub discussion, Grafana user Darth-Bobo described having to maintain the same variables separately across dashboards, warning that configuration differences could become “unmanageable over time”. More recently, an early tester described shared variables as useful for evaluating Git Sync without Terraform templating.

Variables can have global scope, which makes them available throughout a Grafana organisation, or folder scope, which limits them to dashboards in the same folder. An editor can add the available variables from a dashboard sidebar, either individually or all at once. Viewers can still change the selected value on a dashboard, while the variable configuration remains centrally managed.

Teams running Grafana themselves must enable the grafana.dashboardGlobalVariables feature toggle to try the preview. Grafana places the management screen under Dashboards > Variables, separate from the dashboard editor where users add the shared controls.

Notebooks are also in public preview across all editions. A notebook can hold panels from dashboards or Explore alongside written observations, with findings from Grafana Assistant included as well. Teams can use the document to record how they investigated an issue or to prepare a post-incident review with relevant panels already in place.

Users can create a notebook manually or through Grafana Assistant, then save and share it. Grafana is rolling the feature out gradually to Grafana Cloud. Self-managed installations need the dashboard.notebooks feature toggle enabled.

Grafana’s Notebooks joins similar investigation-document workflows from other observability vendors. Datadog Notebooks combines live graphs with rich text and supports simultaneous editing, inline comments and reusable postmortem templates. New Relic Notebooks, generally available since August 2026, combines NRQL queries, visualisations and Markdown, with natural-language query translation and notebook-wide variables.

The release also changes how Grafana Assistant builds dashboards. In public preview, dashboard plans let a user describe what they want to monitor and review a proposed layout in chat before building it. The plan covers the title and the proposed panels, including visualisation types and variables. A read-only preview lets the user refine the plan before choosing to build and save the dashboard.

A separate Assistant feature, Undo turn, is generally available across all editions. It restores the previous dashboard state after an Assistant edit, including when one request changed multiple panels. The Assistant dashboarding guide notes that undo is unavailable if the dashboard has changed since the Assistant’s edit.

Grafana 13.3 also previews a visual refresh with revised themes and interface components. Grafana Labs says the visual refresh preserves existing navigation and workflows and introduces no breaking changes for plugins. Plugins using standard Grafana components and theme tokens pick up the new appearance; those with custom styling can migrate separately. Self-managed users can enable grafana.visualDesignRefresh to try it and switch back to the previous design.

About the Author

Subscribe for MMS Newsletter

By signing up, you will receive updates about our latest information.

  • This field is for validation purposes and should be left unchanged.