I currently use the Grafana Docker image (latest) with provisioned dashboards stored as JSON, which allows me to track changes in Git. This approach works well for version control, but it requires duplicating panels across multiple dashboards.
I’m interested in using Library Panels to avoid this duplication. However, from what I understand, Library Panels require a database backend, meaning I’d need to introduce something like an SQLite database to store the panel definitions.
Is there a way to set up Grafana to use Library Panels without relying on a database backend, so that I can continue managing my dashboards (and Library Panels) as JSON files (or similar) in Git?
Thanks for any help!
Welcome @masonhieb
Even with provisioning, pretty sure you are using a backend db such as sqlite
look in your data folder of your grafana
You’re right, I think I need clarify what I mean: currently people can clone the repo containing the Grafana dashboard JSON files (and this repo contains no SQLite database) and then start up the Grafana Docker container and see those dashboards. When the container starts up it loads up a db backend, but that is created locally.
However, I am wondering if there is a way to use Library Panels in those dashboards without having to save and work with a SQLite database in my git repository? Can they be stored as JSON or something else? Or is the only way for something like this to work to save a database file in my repository?
