What problem does it solve?
Grafana OSS setups can become inconsistent and hard to reproduce when dashboards, data sources, alerting, RBAC, and server settings are managed manually across environments.
Core Features & Use Cases
- Dashboard provisioning: Use file-based provider YAML to load dashboards from a known path and folder structure.
- Data source provisioning: Configure Prometheus, Loki, Tempo, and Pyroscope (among others) via provisioning YAML so panels and queries work consistently.
- Panel building blocks: Select appropriate visualization types (time series, logs, traces, tables, heatmaps, node graphs, etc.) and apply template variables for reusable, environment-aware dashboards.
- Alerting configuration: Enable and configure unified alerting and define how alert evaluation and notification routing behaves.
- RBAC and service accounts: Provision service accounts with roles and tokens to control access for users and automation.
- Server and security settings: Set grafana.ini basics like ports, URLs, auth, admin defaults, and feature toggles.
- Operational APIs: Use Grafana HTTP endpoints to search, fetch, create/update dashboards, manage data sources/users, and create service account tokens.
Quick Start
Use the grafana-oss skill to generate the provisioning YAML and grafana.ini snippets you need to stand up a consistent Grafana instance with preloaded dashboards, Prometheus/Loki/Tempo/Pyroscope data sources, and RBAC service accounts.