Blog

Seamlessly Promote Grafana Dashboards: Tips for Dev and Prod Instances

July 13, 2023

Deepak Kumar

1 Min Read

Click To Explore

For those organizations that use organizations for “prod” and “dev” instances and wanted a dashboard “promoted” or duplicated, manually moving the JSON may not be ideal.

For starters, the simplest way is to go into the database and change org_id for that dashboard. This is unless the data sources are different between the orgs. In that case export/import is the safest.

Another approach is creating folders for each team inside what they have admin rights . Over the org everyone has viewer rights to everywhere to make the sharing is caring possible(what is the point to hide anything in metrics). You can provide dashboards and teams can copy them into their folders and do what they wish there with them. You might also want to backup teams dashboards.

💡

Dig into the differences between SLA vs SLO vs SLI here.

Marcus Olsson, Developer advocate at Grafana suggests another alternative - store the dashboards in your Git, and use provisioning in Grafana to promote and reuse dashboards amongst your teams.

Another option might be to have ansible scripts to deal with all the folders and access. Folders are a much better approach.

Looking for an end-to-end incident alerting, on-call scheduling and response orchestration platform?

Book a demo or Sign up for a 14-day free trial of Xurrent IMR. No CC required. Implement modern incident response and SRE best practices within your production operations and provide industry-leading SLAs to your customers

Partners

A Note From the Road: What SPARK Taught Me About Time

During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

3 Mins

July 1, 2026

Service Management

How Long Should ITSM Implementation Really Take in 2026?

Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.

8 Mins

May 30, 2026