Grafana
Also known as: Grafana Labs, Grafana dashboard, LGTM stack
Grafana is a visualization platform for operational data.
You connect it to Prometheus, databases, cloud services, or any of 150+ data sources, and build dashboards with graphs, gauges, tables, and heatmaps. It's the standard tool for DevOps and platform teams to monitor system health and business metrics.
Grafana, explained at three levels
At home
Grafana is like a car's instrument cluster for your data. The car's sensors (your databases and monitoring tools) keep measuring things, and Grafana doesn't store those readings; it asks each source for the latest numbers and draws them as gauges, graphs, and tables. Each time the dashboard refreshes, it asks again, so you see all the important readings in one place, kept current.
At work
Grafana is open-source dashboard software that connects to many data sources, such as Prometheus, SQL databases, and cloud monitoring services, and displays them together as charts, tables, and alerts. Businesses care because operations, product, and management teams can watch server health, user activity, and business KPIs on one screen without copying data into a new system, and get alerted when numbers cross thresholds.
At home
Grafana panels (graph, bar chart, table, heatmap, stat, gauge) are configured with queries against a connected data source. Dashboards can have variables (dropdowns to filter by environment, region, or service). Alerts can fire when panel values cross thresholds, routing to email, Slack, or PagerDuty.
At work
Grafana supports 150+ data sources: Prometheus, InfluxDB, Elasticsearch, PostgreSQL, MySQL, BigQuery, CloudWatch, Azure Monitor, and more. Loki adds log aggregation (like Elasticsearch but optimized for Prometheus-style label-based querying). Tempo adds distributed trace visualization. Together they form Grafana's LGTM stack (Loki, Grafana, Tempo, Mimir).
At home
Every Grafana dashboard is a JSON document describing panels, queries, and variables, so it can live in Git and be deployed like code. Provisioning files in YAML load data sources and dashboards when Grafana starts, and tools such as Terraform's Grafana provider or the Grafonnet library generate them. Grafana keeps its own configuration in a small database (SQLite by default), while the data stays in the sources. In my view, treating dashboards as code is what keeps them from rotting.
At work
Grafana Enterprise adds fine-grained RBAC, team-level dashboard permissions, reporting (PDF/email), caching, and enterprise data source plugins. Grafana IRM, which absorbed Grafana OnCall, handles on-call scheduling and incident management. At large scale, Grafana's data source query federation and cross-data-source correlations (linking metrics to logs to traces) provide the full observability workflow in one tool.
Real-world examples
At home
Aisha connected Grafana to her home server's Prometheus instance and built a dashboard showing CPU, memory, and disk usage across all her machines. She set an alert to email her if disk usage exceeds 90%.
At work
Carlos's team has a Grafana dashboard with three rows: top row shows infrastructure health (Prometheus), middle row shows application errors (Loki), and bottom row shows business KPIs (PostgreSQL). Every incident review starts with this dashboard.
Common confusions
- Grafana stores your data — Grafana is a visualization layer: it queries data from your existing sources (Prometheus, databases, etc.) but stores nothing itself. Your data stays where it lives; Grafana just reads and displays it.
- Grafana is only for DevOps teams — Any team with data in a supported data source can use Grafana. Product teams track feature usage, finance tracks spending, sales teams monitor pipeline metrics. It's a general-purpose dashboarding tool.
For analysts
Business analysts use Grafana to build executive dashboards by connecting it to a PostgreSQL or BigQuery data source. Dashboards refresh automatically, and variable dropdowns allow filtering by region, product, or time range without modifying queries.
History & origin
Grafana was created by Torkel Odegaard and released in 2014 as a fork of Kibana (part of the ELK stack), redesigned to work with Graphite and then Prometheus. It grew into a standalone project, became company-backed (the company now called Grafana Labs formed in 2014 as Raintank), and expanded from metrics visualization to logs (Loki), traces (Tempo), and a full observability stack. Grafana Cloud launched in 2019 as a managed SaaS version.