Grafana visualizes data from Prometheus, Loki, Elasticsearch and dozens of other sources in shared dashboards, and unifies alerting across them - dashboards defined as code where you want it.
Why teams use it
- One pane of glass across metrics, logs and traces
- Dashboards and alerts as code (provisioning) for reproducibility
- A vast library of community dashboards to start from
Install it
docker run -d -p 3000:3000 --name grafana grafana/grafana-oss
# default login admin/admin on http://localhost:3000A first working config
Provision a data source as code so it is reproducible.
# provisioning/datasources/prometheus.yaml
apiVersion: 1
datasources:
- name: Prometheus
type: prometheus
access: proxy
url: http://prometheus:9090
isDefault: trueRun and verify
# Export a dashboard as JSON so it can be version controlled
curl -s -H "Authorization: Bearer $KEY" \
http://localhost:3000/api/dashboards/uid/abc123 | jq .dashboard > dash.jsonMistakes to avoid early
- Click-built dashboards that live only in the database and vanish on rebuild
- Overloaded dashboards nobody can read during an incident
- Alerting split between Grafana and other tools with no clear owner
Want senior help putting Grafana to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.