Grafana Interview Guide
🟢 Easy (Basics)
1. Grafana?
Observability UI for metrics, logs, traces.
2. Panels & variables?
Dynamic dashboards with templating variables.
3. Annotations?
Overlay events/releases on charts.
4. Alerting?
Unified alerting with contact points/policies.
5. Data sources?
Prometheus, Loki, Tempo, Elasticsearch, CloudWatch etc.
🟡 Medium (Hands‑on)
1. Provisioning as code?
YAML/JSON for datasources/dashboards via git/CI.
2. RBAC/folders?
Organize dashboards and control access.
3. Logs & traces linking?
Jump from metrics to logs/traces by labels/traceID.
4. Performance?
Use recording rules, narrow ranges, cache.
5. Multi‑tenant?
Org/folder isolation or Grafana Cloud.
🔴 Hard (Advanced)
1. SLO dashboards?
Burn‑rate panels using PromQL; error budgets.
2. Auditing changes?
Store dashboards as code; PR review, versioned.
🧪 Scenario Questions & Answers
1. Slow dashboards.
Precompute; reduce panels; limit time range.
2. Team‑scoped access.
Folders per team + datasource permissions.
3. Version & promote.
Git manage JSON; CI provisions per env.
Generated for quick interview revision — basics, hands-on, advanced, and scenarios.