Monitoring

Grafana

Dashboards and alerting for metrics, logs, and traces from any data source — the visualization layer of a self-hosted observability stack.

Activity score (0-100) — weighted from the 4 sub-scores below. Calculated automatically from the GitHub API, refreshed weekly.

Community

100

Development

100

Maintenance

Risk

75,663 GitHub stars Last commit: 1 days ago Last release: 19 days ago Open issues: 3461 License: AGPL-3.0

Hardware

RAM minimum512 MB

RAM recommended2048 MB

CPU idle~0.1 cores

CPU recommended2 vCPU

ARM supportFull

Access & auth

Needs reverse proxy✓ Yes

OIDC support✓ Yes

LDAP support✓ Yes

Multi-user✓ Yes

Mobile appNone

Operations

MaturityStable

Maintenance burdenMedium

Setup difficultyMedium

Backup methodSQLite/Postgres/MySQL DB dump (dashboards + users) + dashboards-as-JSON export

Leaving the cloud

Migration difficultyMedium

Replaces

Cloud provider monitoring consolesDatadog dashboards

Relationships

Install via

Docker ComposeKubernetesNative

Works well with

CaddyTraefik

Recommended backup

Native/Manual

Our notes

Grafana itself is light — the RAM cost of a monitoring stack comes from what feeds it (Prometheus, Loki), not Grafana. OIDC and LDAP are both free in open-source Grafana, no license needed, which makes it easy to put behind Authelia/Authentik. Dashboards-as-code (JSON provisioning) is worth using from day one — clicking through the UI doesn't survive a rebuild.