Provisioning in Grafana | Basics and pitfalls | File examples | Windows and Docker Demo

Provisioning in Grafana significantly simplifies the deployment process. However, configuring provisioning itself might be quite a pain. This video was created to explain the basics of provisioning and provide links to actual provision files that Volkov Labs uses in many open-source projects.

LINKS FROM THE VIDEO

CHAPTERS
0:00 Intro
0:38 What is provisioning
0:56 Grafana UI is one (not the best) alternative to provisioning
1:17 HTTP API is another alternative to provisioning
1:35 How to determine what parts of Grafana can be provisioned
2:48 Let's provision a dashboard
6:13 Let's provision a data source
7:55 Let's provision an alert rule

DISCOVER

GET IN TOUCH

#Grafana #GrafanaPlugins #Visualization #visualización

[volkovlabs]

Share with us your thoughts about this video. What is helpful? Feel free to ask questions about your particular case as well.

[boriskontorovich]

WOW. This is the only video on YouTube that explains provisioning. Thank you Daria!

[Mimmi]

Great video and well explained! Love the way how Daria is presenting the content. Very clear and precise!

[renobodyrenobody]

Thanks for this video. I regret Grafana does not export the datasources allowing us to copy and paste to the provisioning folder, it was a big waste of time on my part.

[googleevil]

Nice work Daria! Looking forward for notification provisioning, once it will be publicly available!

[asmith]

Great video. Is there no easy way to delete a provisioned alert that does not involve going to the CM database?

The Grafana documentation has an extremely brief section where it prompts to create a new yaml file with the alert details present:

deleteRules:
- orgid
- uid

I haven't found anyone who can get this to work

[ArbabShahbaz-rvyd]

Nice, just a quick question.
If we have multiple alert rules and I want to provision only 2 of them, can I export them separately via alert rule modification, so that only that file gets provisioned?
Because the method you used would provision all 10 alert rules if we have them.
Thanks.

[independence_]

Hi,
The dashboard json in uat and prod are different example: within Prometheus query application name between ends are different uat app name suffix ‘-uat ‘, dashboard links - external link different between uat and prod etc if we want to achieve same json between both env with minor difference as mentioned above how can we support this using provisioning please? I tried using environment variables but it doesn’t pick up to meet these requirements.

[rockomax]

is there any sample repo where we can see the required file structure? for example where do I put the config. for contact points? for notification policies?
there is not even a single example where they show the paths in the docs..wth?