Grafana Dashboard Variables: One Dashboard for All

The Problem

You’ve got 3 environments: dev, staging, prod. Each one needs the same dashboard. So you duplicate the dashboard 3 times. Then you add a metric to one. You remember to update the other two. Mostly.

Six months later, the prod dashboard is out of sync with dev. You don’t notice until something breaks.

Grafana variables solve this. One dashboard. Multiple environments. One source of truth.

What Are Dashboard Variables?

Variables are placeholders in your dashboard that change based on user input or data source values. They act as dashboard-level parameters.

Instead of hardcoding job="api" in every query, you use $job. User selects “api”, “worker”, or “scheduler” from a dropdown. The dashboard updates everywhere.

Setting Up Variables

Go to Dashboard Settings → Variables → New Variable.

Here’s a practical example: environment selector.

Name: env
Type: Constant
Value: prod

Wait, that’s boring. Let’s do it better:

Name: env
Type: Custom
Custom Options: dev, staging, prod
Selected Value: prod
Refresh: Never

Now your dashboard has a dropdown with 3 options. When you pick one, $env updates everywhere.

Real Example: Multi-Environment Prometheus Dashboard

You’re monitoring an API across dev/staging/prod. Your Prometheus jobs are labeled:

• job="api-dev"
• job="api-staging"
• job="api-prod"

Step 1: Create Environment Variable

Name: environment
Type: Custom
Options: dev, staging, prod
Default: prod
Multi-select: Off

Step 2: Create Job Variable (Conditional)

This one pulls data from Prometheus based on the environment:

Name: job
Type: Query
Datasource: Prometheus
Query: label_values(up{environment="$environment"}, job)
Refresh: On Dashboard Load

This query says: “Give me all distinct job names where environment matches the selected value.”

Step 3: Use in Panels

In a panel’s Prometheus query:

rate(http_requests_total{job="$job"}[5m])

Or more sophisticated:

rate(http_requests_total{environment="$environment", job=~"$job"}[5m])

Now when a user picks environment=staging and job=api, the dashboard shows staging API metrics. Pick environment=prod, and it shows prod. Same dashboard.

Advanced: Regex Filters

Variables support regex patterns. Suppose you have hosts: host-1, host-2, api-1, api-2. Create a variable:

Name: host_filter
Type: Custom
Options: host-*, api-*, *
Default: host-*

Then in your query:

up{instance=~"$host_filter"}

Pick api-* to see only API hosts. Pick * to see everything.

Multi-Select Variables

Allow users to pick multiple values:

Name: status_codes
Type: Custom
Options: 200, 404, 500, 503
Multi-select: On
Selected Value: [200, 500, 503]

In your Prometheus query, use =~ (regex match):

rate(http_requests_total{status=~"$status_codes"}[5m])

Grafana converts [200, 500, 503] into 200|500|503 (regex OR). Clean.

Templating in Titles

Variables aren’t just for queries. Use them in panel titles:

HTTP Requests - $environment ($job)

When you switch environments, the title updates. Helps prevent confusion.

JSON Variable Example

Here’s what a full dashboard JSON looks like with variables:

{
  "dashboard": {
    "title": "API Monitoring",
    "templating": {
      "list": [
        {
          "name": "environment",
          "type": "custom",
          "options": {
            "values": ["dev", "staging", "prod"]
          },
          "current": {
            "value": "prod"
          }
        },
        {
          "name": "job",
          "type": "query",
          "datasource": "Prometheus",
          "query": "label_values(up{environment=\"$environment\"}, job)",
          "refresh": 1,
          "current": {
            "value": "api"
          }
        }
      ]
    }
  }
}

If you’re version-controlling dashboards (you should be), commit this JSON to git. When you export/import, variables come along.

Pro Tips

Populate Variables from Loki Labels

If you’re using Loki for logs:

Name: service
Type: Query
Datasource: Loki
Query: label_values(job)

Now your log filtering matches your metrics. Consistency across observability.

Use ad-hoc Filters

Toggle Ad-hoc filters on. Users can click labels in graphs to filter. Grafana adds the filters as query parameters in the URL.

https://grafana.local/d/xyz?var-env=prod&var-job=api

Shareable links. Reproducible views.

Chain Variables

A variable’s query can reference another variable:

Name: pod
Query: label_values(kube_pod_labels{namespace="$namespace"}, pod)

User picks namespace, pod list updates. Powerful.

Common Gotchas

Variable not updating? Check the query. If it has a syntax error, it silently fails. Check the Prometheus console directly.

Multi-select not working in PromQL? Use =~ for regex match, not =. Grafana converts [a, b] into a|b (regex).

Want to hide a variable from users? Use a Constant type. It won’t show in the UI but still updates queries.

The Payoff

One dashboard. Any environment. Any subset of services. Users can troubleshoot without bugging you for dashboard links.

It’s 30 minutes of setup. Saves hours of maintenance.

Do it.

Chaining Variables

Variables can depend on each other. Select a datacenter and the host list updates automatically:

1. Create $datacenter variable (query: label_values(up, datacenter))
2. Create $host variable (query: label_values(up{datacenter="$datacenter"}, instance))

Now $host only shows hosts in the selected $datacenter. No more filtering through 200 hosts when you only care about one region.

This is the feature that makes dashboards actually useful instead of overwhelming.

Common Questions

Why does my Grafana multi-select variable not work in PromQL?

Use the =~ regex match operator instead of = in the query. Grafana converts a multi-select value like [200, 500, 503] into the regex 200|500|503, so the PromQL label matcher must be a regex. For example, write status=~"$status_codes" in the rate query.

How do I hide a Grafana variable from dashboard users?

Give the variable the Constant type. A Constant variable does not show in the dashboard UI, but Grafana still substitutes its value into your queries. For example, a variable with Name env, Type Constant, and Value prod turns every $env in the dashboard’s queries into prod.

Can one Grafana variable depend on another variable?

Yes. A variable’s query can reference another variable. For example, a $host variable using label_values(up{datacenter="$datacenter"}, instance) only lists hosts in the chosen datacenter. When the user picks a different datacenter, Grafana updates the host list to match, so nobody filters through 200 hosts to find one region.

How do I share a Grafana dashboard link with variables already selected?

Turn on Ad-hoc filters. Grafana then adds the selected filters to the dashboard URL as query parameters, such as ?var-env=prod&var-job=api. Copy that URL, and anyone who opens the Grafana dashboard link sees the same selections. The result is a shareable link and a reproducible view.

Related Reading

• Observability and Monitoring for Containers
• Beszel: Server Monitoring Without the Prometheus Tax
• Grafana Alloy: Replacing the Agent After Deprecation
• Promtail to Alloy Migration: A Practical Diff
• Supercharge Your Homelab Monitoring with Zabbix