← All insightsConcepts

Grafana: core concepts and configuration explained

CodeWizard Academy · 18 May 2026 · 3 min read · Beginner

The open dashboarding layer for metrics, logs and traces, with alerting across many data sources. This walkthrough covers the mental model and the configuration you will actually touch.

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.

The configuration that matters

Provision a data source as code so it is reproducible.

yaml
# provisioning/datasources/prometheus.yaml
apiVersion: 1
datasources:
  - name: Prometheus
    type: prometheus
    access: proxy
    url: http://prometheus:9090
    isDefault: true

Principles to hold onto

  • Provision data sources and dashboards as code from Git
  • Design a few focused dashboards per service, not one giant wall
  • Standardize variables and folders so teams find things fast

Everyday commands

bash
# 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.json

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.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult