Grafana Associate case studies
Grafana Associate · Put your knowledge to work in context.
This page is an independent, unofficial study resource for people preparing for the Grafana Associate credential. It is written for dashboard authors, SREs, platform engineers, and observability practitioners who build panels, wire up data sources, and share dashboards with teammates, and who want a structured way to check their working knowledge before sitting a Grafana-focused exam. The practice material here is organised around four areas: Grafana fundamentals and navigation, data sources and queries, panels and visualization, and dashboards, variables, and sharing. Each area is weighted evenly in this study plan, so expect to spend comparable time on query construction, panel configuration, and dashboard-level features such as template variables and sharing options rather than on any single topic. The Grafana Associate case studies are 5 cases and about 2,962 words.
1Dashboard link fails across organizations
A platform team runs Grafana 10.4 with two organizations, Platform and Web. Priya is a Viewer in both.
570 words, about 3 min2PostgreSQL panel returns no rows with epoch milliseconds
An SRE team monitors checkout latency with Grafana 11 and a PostgreSQL data source. The table checkout requests has columns id, created at (bigint, Unix epoch milliseconds), region (text), and duration ms (integer).
632 words, about 3 min3Latency spikes disappear on a seven-day panel
A product team has a time series panel showing p95 request latency from Prometheus. The dashboard time range is Last 7 days, refreshes every minute, and the panel has Max data points set to 100 and Min interval set to 30m by a previous owner.
612 words, about 3 min4Multi-value instance variable returns no data
An operations team maintains a Grafana dashboard with two template variables. region is a custom variable with values eu , us , and apac , multi-value enabled, and an All option.
575 words, about 3 min5Dashboard import breaks data source references
A platform team maintains 40 dashboards in a staging Grafana 11 instance and needs to promote them to production. Both environments use Prometheus and Loki, but each data source was created manually, so UIDs differ, for example prom-stg-7f2 versus prom-prod-91c .
573 words, about 3 min