Skip to content

Weekly

Get a weekly list of changed dashboards

Each Sunday you get a record of which dashboards were edited that week, so changes don't go unnoticed.

Runs
Weekly
Apps
Grafana Cloud
AI
Not needed
Access
Viewer

Send this to your assistant

Create a ClickRuntime automation: every Sunday evening email me a list of Grafana dashboards that changed this week, with the version number and who saved it.

Paste it into your assistant. It tells you what it will send or change before it runs live.

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Grafana dashboards are code-like assets that grow by accident. Someone tweaks a panel query during an incident, another person saves over a layout, and a few weeks later the on-call engineer cannot find the graph they remember. Without version control around your dashboards, a deleted folder or a bad import can erase months of careful work, and rebuilding from screenshots is miserable.

Once a week your Grafana Cloud dashboards are searched, each one's version is compared with the one stored from last time, and an email goes out describing what changed: which dashboards are new, edited or gone. It gives you a regular record of what your monitoring looked like.

It suits platform teams and small companies that rely on Grafana but have never set up provisioning or Git sync.

What you get out of it

  • A safety net against accidental edits

    If a panel is overwritten or a dashboard is removed, you know within a week and which one it was, instead of discovering it during an outage. Knowing which one changed makes it easy to fix quickly.

  • Visibility into who is changing monitoring

    A weekly list of edited dashboards shows when the monitoring setup shifts, which helps engineering leads keep standards. Engineering leads can see when the monitoring setup shifts, who tends to change what, and whether standards for naming and folders are being kept. A weekly list makes that conversation easy and factual.

  • Faster recovery from deletion

    With a record of which dashboards existed and their versions, restoring a lost dashboard is a matter of finding it, not guessing. With a record of existing dashboards and their versions, restoring a lost one means finding it in the email, not reconstructing it from half-remembered queries and screenshots taken during an incident.

  • New dashboards get noticed

    Newly created dashboards appear in the email, so duplicates and one-off experiments are visible before they clutter the folder. Newly created dashboards appear in the weekly email, so duplicates, test copies and one-off experiments are visible early. That keeps your shared folders from filling up with clutter that nobody owns.

  • Evidence for reviews after incidents

    When asking what the graphs looked like on a given week, you have a dated email to answer with. When someone asks what a graph looked like a few weeks back, there is a dated email that answers the question, and a record to learn from after an incident review.

How it works

What happens, step by step

  1. Every Sunday, ClickRuntime goes through your Grafana dashboards and checks each one's version number.

  2. It compares them with the versions it saved last week to find the dashboards that were edited.

  3. You get an email listing each changed dashboard with its new version, who changed it and when. The new versions are saved for next week's check.

Before it runs live

  • Connect Grafana Cloud

What you get

RunsWeekly
Get a weekly list of changed dashboardstoday, 9:00Succeeded
Email · Dashboards changed this weekCheckout overview: v42 by admin on Thu 16 Oct API latency: v7 by sre-bot on Mon 13 Oct

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

  • Run it at a different time, more or less often, or only on weekdays
  • Add an AI step, for example to summarize, sort or draft a reply
  • Add another app, for example also send it to Slack
  • Combine it with other Grafana Cloud steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
email_a_weekly_backup_of_dashboards.pyexample
from datetime import datetime, timedelta, timezone
from clickruntime import on_trigger, credentials, http, notify

GRAFANA = "https://acme.grafana.net"

@on_trigger
def run(event):
    headers = {"Authorization": f"Bearer {credentials.secret('GRAFANA_TOKEN')}"}
    since = datetime.now(timezone.utc) - timedelta(days=7)
    found = http.get(f"{GRAFANA}/api/search", params={"type": "dash-db", "limit": 5000}, headers=headers).json()
    changed = []
    for d in found:
        full = http.get(f"{GRAFANA}/api/dashboards/uid/{d['uid']}", headers=headers).json()
        updated = datetime.fromisoformat(full["meta"]["updated"].replace("Z", "+00:00"))
        if updated >= since:
            changed.append(f"{d['title']}: v{full['dashboard']['version']} by {full['meta']['updatedBy']} "
                           f"on {updated:%a %d %b}\n  {GRAFANA}{d['url']}")
    notify.email_me(f"{len(changed)} Grafana dashboards changed this week", "\n".join(changed) or "No changes.")
    return {"changed": len(changed), "total": len(found)}

FAQ

Common questions

Does the email contain the full dashboard JSON?
The email lists changes by dashboard and version. Whether to attach the full JSON is a choice you can ask for, which suits teams that want to restore from the email itself. Large attachments can be heavy, so the default stays short.
Does it need a Grafana Cloud admin account?
It needs a service account token that can read dashboards, which is stored as a secret. Read access is enough, and the workflow never changes your dashboards. Keys are stored as secrets, and nothing is changed in Grafana while it runs. Admin rights are not needed for this.
What if nothing changed this week?
You can still receive a short note saying so, or no email at all if you prefer quiet weeks. Confirming that nothing changed is itself useful to some teams. Either way, you get a regular signal that the check ran, which is reassuring if you worry about a silent failure.
What permissions does it need?
Viewer. Nothing else in your accounts is used.
Does it need AI?
No. It runs without AI, so it doesn't use your plan's AI allowance.
How many runs does it use?
One run each time it runs (weekly). Checks that find nothing to do and stop right away aren't counted.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Set up “Get a weekly list of changed dashboards” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.