Grafana as Code-An Open Source Observability Solution
summary
An open-source observability stack is deployed and maintained as code using kube-prometheus-stack via Helm, with Grafana sidecars that read ConfigMaps/Secrets (labelled Grafana sidecar data_source=true) to provision data sources, dashboards and alerts so pods can be recreated without losing config. Logs ship with Promtail into Loki -> S3 storage, letting cheap object storage hold months of logs and return thousands of lines in seconds. Argo CD applies environment-specific YAML; alert export/import is clunky and documentation and team ownership require extra work.
AI-written summary · about
chapters (13)
- 0:00Introduction to Grafana as Code
- 1:12Solution objectives and overview
- 2:13Observability pyramid explained
- 3:58Data sources in Grafana
- 5:47Sidecar concept for persistence
- 8:18Dashboards as code
- 10:02Alerts as code
- 12:13Downsides of the approach
- 13:18Grafana Loki for logs
- 16:32Additional deployment features
- 17:14GitOps with Argo CD
- 20:26Summary and conclusion
- 21:09Q&A session
related talks
36mObservability at Scale With Monitoring as Code...
34mThe Grafana Stack: Building a Highly Available, Scalable Observability Platform
13mArchitecting an open observability stack
01h 02mDesigning an open-source observability stack for Kubernetes
29mParanoid Observability –Success Stories and Misfortunes observing an observability stack
27mFrom Zero Visibility to Full Observability with Grafana
27mMonitoring as Code: Managing your Observability Assets the Cloud-Native Way
31mService cockpit - developer friendly Grafana based monitoring aggregator