Grafana Scenario-Based Interview Questions (2027)

40 Grafana scenario interview questions: no-data panels, slow dashboards, alert routing, provisioning, access, HA and on-call drills.

Sep 13, 2025 - 15:32
Nov 7, 2026 - 18:01
 0  111
Grafana Scenario-Based Interview Questions (2027)

Grafana scenario-based interview questions give you a real problem, such as a blank panel, a slow dashboard, an alert that never fires or a dashboard someone deleted, and ask how you would solve it. Strong answers check the data source and query first, then the panel, then permissions and provisioning. This page has 40 Grafana scenarios grouped by experience level.

The scenarios focus on Grafana itself: dashboards, queries, alerting, provisioning, access and operations. For the metrics side, pair this page with our scenario-based Prometheus interview questions, and for how the two tools fit together read using Prometheus and Grafana together.

Key takeaways

  • Most "Grafana is broken" problems are data source or query problems. Use the panel's query inspector before anything else.
  • Grafana Alerting is built from alert rules, contact points, notification policies, silences and mute timings. Interviewers expect these names.
  • Dashboards, data sources and alerting resources can be provisioned from files or managed through the HTTP API and Terraform, which makes them reviewable in Git.
  • Template variables, sensible time ranges and recording rules in the data source are the main tools for slow dashboards.
  • Access is controlled through organizations, teams, folder permissions and roles. Senior answers mention service accounts instead of personal API keys.

How to answer a Grafana scenario

LayerQuestion to askWhere to look
Data sourceCan Grafana reach it and authenticate?Data source "Save and test", server logs
QueryDoes the query return data for this time range?Query inspector, Explore
PanelAre units, transforms and overrides hiding data?Panel editor, Table view
AccessCan this user see the folder and data source?Folder permissions, teams, roles
ConfigIs the item provisioned or managed elsewhere?Provisioning files, Terraform, API

Grafana scenario questions for freshers

1. A panel shows "No data". What do you check first?

Open the query inspector to see the exact request and response. Then widen the time range, run the same query in Explore, and confirm the data source test passes. If the raw response has data, the problem is in the panel: a transform, a filter or a wrong field. If it does not, fix the query or the data source.

2. You added a Prometheus data source and "Save and test" fails. What is wrong?

Usually the URL. Grafana's backend makes the request, so the URL must be reachable from the Grafana server, not from your browser. In Docker or Kubernetes, use the service name (for example http://prometheus:9090) instead of localhost. Then check authentication and TLS settings.

3. A graph shows values that look 1,000 times too big. How do you fix it?

Set the correct unit in the panel's standard options (for example milliseconds rather than seconds, or bytes). Grafana scales the axis by unit. If the query itself returns the wrong scale, fix it in the query.

4. Users want one dashboard for every server instead of one per server. How do you build it?

Create a query variable that lists instances from the data source, such as label_values(up, instance) for Prometheus, and use $instance in panel queries. Enable multi-value and "Include All" if users need several servers at once, and use panel repeat to draw one panel per value.

5. A teammate's dashboard looks different on your screen. Why?

Likely different time range, time zone, variable values or a browser-level refresh setting. Share a link with the time range and variables included, or set the dashboard's default time zone and save current variable values as defaults.

6. Someone deleted a dashboard by mistake. Can you get it back?

Check whether your Grafana version has recently deleted dashboards available for restore, then check backups and Git if the dashboard was provisioned or exported. Dashboard version history only helps for edits, not after deletion. The lasting fix is to keep important dashboards as code.

7. A dashboard refreshes every 5 seconds and the data source is struggling. What do you change?

Raise the refresh interval to match how often data changes (often 30 seconds to a minute), and set min_refresh_interval in the server configuration so users cannot choose very short intervals.

8. You need to show the latest value of a metric as a big number. Which panel?

The Stat panel, with the calculation set to "Last" (or "Last not null") and thresholds for colour. Use the Gauge panel if a visual range helps.

9. Logs and metrics are in separate tools. How do you look at both together in Grafana?

Add a logs data source such as Loki or Elasticsearch, use Explore with split view to compare metrics and logs for the same time range, and add a logs panel to the dashboard filtered by the same variables.

10. You want to mark deployments on graphs. How?

Use annotations. Create them through the HTTP API from your CI/CD pipeline at deploy time, or define an annotation query against a data source that records deployments.

Scenarios for 2 to 5 years of experience

11. An alert rule should fire but never does. How do you debug it?

Open the rule, preview the query and condition, and check the evaluation history. Confirm the threshold expression, the pending period (the rule must stay in breach for that long), and how "No data" and "Error" states are configured. If the rule fires but nobody is notified, the issue is in notification policies or the contact point.

12. Alerts fire but go to the wrong Slack channel. Where do you look?

The notification policy tree. Policies match alerts by labels and route them to contact points; the first matching child policy wins unless "continue matching" is set. Check the alert's labels against the matchers, then test the contact point.

13. The on-call team is flooded with one notification per pod. How do you reduce noise?

Group notifications in the policy by labels such as alertname and cluster so related alerts arrive as one message, tune group wait and group interval, and review whether the rule should alert on a service-level symptom rather than each pod.

14. Alerts should not page anyone during a planned maintenance window. What do you use?

Create a silence that matches the affected labels for the maintenance period. For recurring windows, such as weekly patching, use mute timings attached to the notification policy.

15. A dashboard with 40 panels takes 30 seconds to load. How do you speed it up?

Reduce the number of panels or collapse rows that load on demand, lower the default time range, use variables so each query covers fewer series, set a sensible min interval, and move expensive calculations into recording rules in Prometheus. Check the query inspector for the slowest queries first.

16. A variable dropdown takes ages to load. Why?

The variable query scans too many series or refreshes on every time change. Narrow the query with a label filter, chain it from a parent variable, and set refresh to "On dashboard load" if the values rarely change.

17. You need the same dashboards in dev, staging and production. How do you avoid manual copying?

Keep the dashboard JSON in Git and provision it through files in Grafana's provisioning/dashboards folder or through the Terraform Grafana provider. Use a data source variable so the same dashboard can point at each environment's data source.

apiVersion: 1
providers:
  - name: team-dashboards
    folder: Platform
    type: file
    allowUiUpdates: false
    options:
      path: /var/lib/grafana/dashboards

With allowUiUpdates: false, edits must go through Git, which keeps environments the same.

18. Data sources must be created automatically when Grafana starts in Kubernetes. How?

Mount a data source provisioning file into provisioning/datasources through a ConfigMap, with secrets injected from environment variables or a Secret. The official Grafana Helm chart supports this through values.

19. A team wants to edit a provisioned dashboard in the UI and keep the change. What do you tell them?

Provisioned dashboards are overwritten from the source on restart or rescan. They should export the JSON and open a pull request, or work on a copy and promote it through Git.

20. You need to combine data from two data sources in one panel. How?

Use the Mixed data source to run queries against both, then use transformations such as "Join by field" or expressions to combine them. Check that timestamps line up.

21. A table panel needs a calculated column. Where do you add it?

Use the "Add field from calculation" transformation, or calculate in the query if the data source supports it. Doing it in the query is usually faster for large results.

22. Developers want to jump from a slow request in a graph to its trace. How?

Configure exemplars on the Prometheus data source with a link to the tracing data source (such as Tempo or Jaeger), and set up data links or trace-to-logs correlations so users can move between metrics, traces and logs.

23. Dashboard JSON is huge and hard to review in pull requests. What helps?

Generate dashboards from code with Grafonnet (Jsonnet) or the Grafana Foundation SDK so reviewers see a short source file, and keep the generated JSON out of review.

24. Users see "Permission denied" on a dashboard their team should see. What do you check?

The folder permissions, the user's team membership and organization, and data source permissions if your edition uses them. Dashboards inherit permissions from their folder, so fix it at folder level.

25. A CI job needs to create annotations and upload dashboards. What credentials do you give it?

A service account with the smallest role that works and a token stored in the CI secret store. Service accounts replaced the older API keys in current Grafana versions and are not tied to a person who might leave.

Senior Grafana scenarios

26. Grafana must stay available if one pod dies. How do you design it?

Run several Grafana replicas behind a load balancer with a shared external database (MySQL or PostgreSQL) instead of the default SQLite file, and configure alerting high availability so instances share alert state and do not send duplicate notifications.

27. How would you organise dashboards for 30 teams?

One folder per team or service with folder permissions, a small set of shared "golden signals" dashboards built from a template, naming and tagging rules, and an owner field in each dashboard description. Clean up dashboards with no views on a schedule.

28. Leadership wants SLO dashboards. How do you build them?

Define the SLI as a ratio of good to total events (for example successful requests over all requests), use recording rules to compute it, and show availability against the target and the remaining error budget. Alert on burn rate rather than raw error count. Our post on observability for SLIs and SLOs covers the background.

29. Alert rules are scattered across Grafana and Prometheus. How do you rationalise them?

Choose one place for each type: for example Prometheus rules for infrastructure alerts managed in Git, and Grafana-managed rules for alerts that combine data sources. Keep one routing configuration so notifications follow the same policy tree.

30. Alerting configuration must be reviewed like code. How?

Provision alert rules, contact points, notification policies and mute timings from files, or manage them with the Terraform Grafana provider, and apply changes through CI after review.

31. A Grafana upgrade broke several panels. How do you plan upgrades from now on?

Read the release notes and breaking changes for each version, run the new version in staging against a copy of the production database, check key dashboards and alert rules there, back up the database before upgrading production, and keep the previous image ready for rollback.

32. Security asks for single sign-on and removal of local accounts. What do you configure?

Set up OAuth, SAML or LDAP authentication, map identity provider groups to Grafana teams and roles, disable the login form and basic auth where policy requires, and keep one break-glass admin account stored securely.

33. A sensitive dashboard must not be shared publicly. What controls exist?

Restrict folder permissions, disable or limit public (shared) dashboards in the server configuration, and audit who can create share links. Make sure snapshots do not include sensitive values.

34. You need to monitor Grafana itself. What do you watch?

Grafana exposes Prometheus metrics at /metrics. Watch HTTP request latency and errors, data source request durations, alert evaluation failures and database health, and alert if Grafana stops being scraped.

35. Costs rose after teams added high-cardinality dashboards. How do you respond?

Find the heaviest queries from data source and Grafana metrics, work with teams to drop unbounded labels such as user IDs, add recording rules for common aggregations and set query limits in the data source.

On-call drill scenarios

36. During an incident every dashboard is blank. What do you check?

Whether the data source (often Prometheus) is down or overloaded, since Grafana only draws what it gets. Check Grafana's server logs, the data source health and network between them. Keep one simple status dashboard that uses a different data source.

37. An alert keeps flapping between firing and resolved. How do you fix it?

Add or lengthen the pending period, use a longer query window or an average instead of an instant value, and if your version supports it set "keep firing for" so short recoveries do not resolve the alert.

38. Notifications stopped after someone rotated a Slack token. How do you recover and prevent it?

Update the contact point with the new token, send a test notification, and keep a watchdog alert that always fires to a separate channel so a silent notification path gets noticed.

39. Grafana fails to start after a config change. Where do you look?

The server log, which reports the provisioning file or setting it could not parse. Revert the change, validate YAML files before deploying, and keep configuration in Git so you can see what changed.

40. A dashboard shows a traffic drop that business teams say did not happen. How do you verify?

Check scrape gaps (the up metric), query step and interval settings, timezone, and whether a deploy changed metric names or labels. Compare with another source such as load balancer logs before declaring an incident.

How to practise these scenarios

Run Grafana and Prometheus with Docker Compose, provision one data source and one dashboard from files, then break them: wrong URL, wrong unit, a notification policy that routes nowhere. Fix each one using the five layers above. Our Prometheus and Grafana training covers these labs in Pune and live online. For tool choices, see top observability tools for DevOps, and for the full interview hub, the 200+ DevOps interview questions guide.

Frequently asked questions

What is the first thing to check when a Grafana panel shows no data?

Open the query inspector to see the raw request and response, then test the query in Explore with a wider time range.

What are the parts of Grafana Alerting?

Alert rules, contact points, notification policies, silences and mute timings. Rules decide when to fire, policies route alerts by labels and contact points deliver them.

How do you keep Grafana dashboards in version control?

Store the JSON in Git and load it with file provisioning or the Terraform Grafana provider, or generate it with Grafonnet or the Foundation SDK.

How do you make a slow Grafana dashboard faster?

Use fewer panels, shorter default time ranges, variables to narrow queries and recording rules for expensive calculations.

How do you run Grafana in high availability?

Run several instances with a shared MySQL or PostgreSQL database behind a load balancer and enable alerting high availability.

Should automation use API keys or service accounts?

Service accounts with tokens. They are the current mechanism for machine access in Grafana and are not tied to a personal user.

Official references

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Mridul I am a passionate technology enthusiast with a strong focus on DevOps, Cloud Computing, and Cybersecurity. Through my blogs at DevOps Training Institute, I aim to simplify complex concepts and share practical insights for learners and professionals. My goal is to empower readers with knowledge, hands-on tips, and industry best practices to stay ahead in the ever-evolving world of DevOps.