How are folks managing their Grafana dashboards? Templating JSON isn’t the one.
I had intended to go the path of version controlled dashboards w/ infra-as-code methodology but @Jeremy (Cloud Posse) made some good points on why that route is pain (specifically around updating dashboards). at the moment we’re just doing click-ops dashboard creation in the ui saved to a remote RDS db.
@joshmyers Grafana dashboards are things where we do not want drift detection to undo ClickOps changes: we want people to be able to customize the dashboards via the Grafana UI.
We have a script in Geodesic called grafana-db we use to upload dashboards from various sources to Grafana via the Grafana API, and have Grafana store them in a remote database. This solves the problem of importing published dashboards in a way that makes them editable. For our installation, we maintain a script that loads the Grafana API key and runs
grafana-db for every dashboard source we want.
Geodesic is a cloud automation shell. It's the fastest way to get up and running with a rock solid, production grade cloud platform built on top of strictly Open Source tools. ★ this repo! h…
Yeah, that isn’t gonna cut it for us. 100+ microservices that we want dashboards for so want something to generate via code
Using https://github.com/grafana/grafonnet-lib + https://github.com/alxrem/terraform-provider-jsonnet is interesting, get a nice diff of the plans etc
heh, this is quite nice actually