Daily
Get a morning list of firing Datadog monitors
Every day you see which monitors are in Alert or Warn, without opening Datadog.
- Runs
- Daily
- Apps
- Datadog
- AI
- Not needed
- Access
- monitors_read
Send this to your assistant
Create a ClickRuntime automation: every day at 8am, email me the Datadog monitors that are currently in Alert or Warn, with the monitor name, status and the service it covers.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Datadog monitors are meant to be acted on, yet many teams carry a backlog of monitors in Alert or Warn that nobody owns. Some are real problems waiting for a fix, some are stale thresholds, and some are noise that trains people to ignore the page. Without a regular review, the dashboard is permanently red and meaningless.
Each morning, this searches Datadog for monitors whose status is Alert or Warn and emails you the list. You see what is currently wrong, in one place, before the day's work begins.
Site reliability engineers, engineering managers and on-call leads use it as a daily check on operational health. The list comes from a search on monitor status in Datadog, so it shows what is currently in Alert or Warn, in the form of one email you can read in a minute.
What you get out of it
Start the day knowing what is wrong
A morning list of triggered monitors shows what needs attention now. Nothing depends on someone happening to open the monitors page. The day begins with a clear view of what is wrong, and nothing depends on someone happening to open the monitors page.
Find monitors nobody owns
A monitor that stays in Alert every day is either a real unresolved problem or a bad threshold. Seeing it daily forces a decision. A monitor in Alert every day is either an unresolved problem or a bad threshold, and seeing it daily forces a decision.
Reduce alert fatigue over time
Noisy monitors stand out in the daily list. Fixing or deleting them makes future alerts more trustworthy. Noisy monitors stand out in the daily list, and fixing or deleting them makes future alerts more trustworthy.
Brief managers without dashboards
Leaders get a plain list they can read in a minute. They understand the state of production without learning Datadog's interface. Leaders get a plain list they can read in a minute, and understand production health without learning the Datadog interface.
Support handovers between teams
A daily record of what was alerting helps the next shift. They know what was already visible when they arrived. A daily record of what was alerting helps the next shift know what was already visible when they arrived.
How it works
What happens, step by step
Every day ClickRuntime checks your Datadog monitors.
It keeps the ones currently in Alert or Warn.
You get an email listing each one with its status and service, without opening Datadog.
Before it runs live
- Connect Datadog
What you get
Build your own
Need it to work differently?
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 Datadog steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_trigger, credentials, http, notify
DD = "https://api.datadoghq.com"
def dd(path, **params):
resp = http.get(f"{DD}{path}", params=params, headers={"DD-API-KEY": credentials.secret("DD_API_KEY"),
"DD-APPLICATION-KEY": credentials.secret("DD_APP_KEY")})
resp.raise_for_status()
return resp.json()
@on_trigger
def run(event):
monitors = dd("/api/v1/monitor/search", query="status:(alert OR warn)", per_page=100)["monitors"]
lines = []
for m in monitors:
service = next((t.split(":", 1)[1] for t in m.get("tags", []) if t.startswith("service:")), "-")
lines.append(f"{m['status']}: {m['name']} (service: {service})")
notify.email_me(f"{len(lines)} Datadog monitors alerting", "\n".join(lines) or "All monitors OK.")
return {"alerting": len(lines)}FAQ
Common questions
Does it include muted monitors?
Can it be limited to certain tags or teams?
Which Datadog keys does it need?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Get a weekly reminder of muted monitors
Each Monday you see monitors that are muted or under a downtime, so nothing stays silenced by accident.
See how it worksGet alerted when Datadog usage jumps
If log or host usage climbs well above normal, you hear about it the same day.
See how it worksGet a weekly SLO and error budget report
Every week you see each SLO's status and how much error budget is left, with the ones below target flagged.
See how it worksKeep exploring
Set up “Get a morning list of firing Datadog monitors” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.