Grafana¶

Home | Knowledge Hub | Projects Hub

Summary¶

Grafana is the industry-standard open-source platform for observability and data visualization. Originally created by Torkel Ödegaard in 2014 as a fork of Kibana, it has evolved from a pure dashboarding tool into the centerpiece of a composable, full-stack observability ecosystem — the LGTM stack (Loki, Grafana, Tempo, Mimir) — with an optional fifth pillar, Pyroscope for continuous profiling.

Grafana connects to virtually any data source through its extensible plugin architecture and provides a single pane of glass for metrics, logs, traces, and profiles. It is built with Go (backend) and TypeScript/React (frontend), licensed under AGPL-3.0, and backed by Grafana Labs, a $6B+ valued company (as of 2024).

Attribute	Detail
Repository	github.com/grafana/grafana
Stars / Forks	73.1k ⭐ / 13.7k 🍴
Commits / Releases	68,000+ commits / 606 releases
Latest Version	v12.4.2 (March 2026)
Languages	TypeScript (50.3%), Go (43.0%)
License	AGPL-3.0 (open-source; plugins mostly Apache 2.0)
Founded	2014 by Torkel Ödegaard
Company	Grafana Labs (est. 2014, HQ: New York)

Evaluation¶

Why it's better: Vendor-neutral, open-standards-first (Prometheus, OpenTelemetry), extremely extensible plugin ecosystem (100+ data sources), and can unify all telemetry signals (metrics, logs, traces, profiles) in a single interface. No other tool matches its breadth of data-source support combined with open-source availability.
When it fits (Applicability): Any team or organization that needs to visualize, correlate, and alert on data from heterogeneous sources. It shines when: you want to avoid vendor lock-in, you use Prometheus/OTel, you need custom dashboards, or you want one tool that connects infra, apps, and business metrics.
Pros and Cons:

Pros	Cons
Unmatched data-source flexibility	Higher operational overhead when self-hosting the full LGTM stack
World-class visualization engine	AGPL-3.0 may create compliance friction for some orgs
Massive community and plugin catalog	Unified alerting is powerful but has a steep learning curve
Open standards (Prometheus, OTel native)	Default SQLite backend limits single-node scale
Free tier in Grafana Cloud is generous	Enterprise features (fine-grained RBAC, SAML) require paid tier
Cross-signal correlation (metrics ↔ logs ↔ traces)	Dashboard sprawl is a real governance challenge at scale

Common Use Cases:
Infrastructure monitoring (Kubernetes, VMs, networks)
Application Performance Monitoring (APM) via Tempo/OTel
Log aggregation and exploration via Loki
Business metrics dashboards (SQL, Elasticsearch, BigQuery)
IoT and industrial telemetry visualization
Security dashboards (with Elasticsearch/Loki SIEM patterns)
AI/ML pipeline observability (emerging, 2025+)
Licensing & Commercial Use:
Core Grafana: AGPL-3.0 (since April 2021; was Apache 2.0 before)
Plugins, agents, SDKs: mostly Apache 2.0
You may use unmodified Grafana commercially. If you modify the source and offer it as SaaS, you must release modifications under AGPL-3.0.
Grafana Cloud tiers: Free ($0), Pro ($19/mo base + usage), Enterprise ($25k+/yr)
Managed alternatives: AWS Managed Grafana (per-user pricing), Azure Managed Grafana (resource-based pricing)
Ecosystem & Data Connections:
Native backends: Prometheus, Loki, Tempo, Mimir, Pyroscope
First-party data sources: Elasticsearch, InfluxDB, MySQL, PostgreSQL, CloudWatch, Azure Monitor, Google Cloud Monitoring, Jaeger, Zipkin, Graphite, OpenSearch, and dozens more
Plugin catalog: 100+ community and enterprise plugins
Collection: Grafana Alloy (OTel Collector distribution), Grafana Agent (legacy)
IaC: Official Terraform provider, Helm charts, Ansible roles
APIs: Full REST API, provisioning YAML/JSON, gRPC (plugin ↔ server)
Compatibility & Requirements:
Runs on Linux, macOS, Windows, Docker, Kubernetes
Backend database: SQLite (default), MySQL 5.7+, PostgreSQL 12+
Browser: Modern Chrome, Firefox, Edge, Safari
Min resources (single node): 1 CPU, 512 MB RAM
Recommended production: External DB (PostgreSQL), Redis for sessions, horizontal scaling behind LB
Alternatives:
Datadog — All-in-one SaaS, higher cost, faster time-to-value
Kibana — Strong for log-centric / ELK-native workflows
New Relic — SaaS APM with generous free tier
Chronograf — Niche, InfluxDB-specific
Apache Superset — Open-source BI focus, less real-time
SigNoz — Open-source, OpenTelemetry-native observability
Splunk Observability — Enterprise, expensive
Migration & Lock-in Risks:
Low lock-in on the visualization layer — dashboards are portable JSON, data sources are external
Moderate lock-in if you adopt the full LGTM stack — Loki's LogQL, Mimir's remote-write API, and Tempo's TraceQL are Grafana-specific query languages, though all backends use open storage formats (object storage, Prometheus TSDB)
Migration from Datadog/New Relic → Grafana Cloud is well-documented
Terraform provider enables IaC portability
Community Health & Support:
One of the top-50 most-starred Go projects on GitHub
73.1k stars, 13.7k forks, 68k+ commits, 1.2k watchers
Active: 3.2k open issues, ~700 open PRs
Strong community: community.grafana.com, Slack, X/Twitter
Enterprise SLAs available through Grafana Labs
Regular release cadence: monthly minor releases, quarterly majors

Notes In This Folder¶

LGTM Stack — the full observability stack built around Grafana (Loki, Grafana, Tempo, Mimir, Pyroscope)
VictoriaMetrics — alternative metrics backend, often compared to Mimir
Prometheus — the de-facto metrics standard that Grafana was built around
OpenTelemetry — the industry-standard telemetry collection framework; Grafana Alloy is an OTel distribution

Assets¶

Store local images, diagrams, and PDFs in the _assets/ subfolder. Prefer Mermaid for inline diagrams.

Next Actions¶

Create comparison notes: Grafana vs Datadog, Grafana vs Kibana
Research Grafana's AI/ML features (Sift, LLM plugin) in depth
Benchmark Grafana Cloud vs self-hosted LGTM at various scales