Skip to content

Automate Datadog

Turn Datadog's monitors, SLOs and usage figures into short reports the team will actually read. Monitors stuck in Alert or Warn, monitors someone muted and forgot, spikes in log ingestion and weekly error budget status arrive by email or chat. Let your AI assistant know what to report, check the plan before it starts, and it keeps reporting on its own.

Try asking

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.

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

Build your own

Build any Datadog automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Datadog should do in your own words, with your conditions, other apps or an AI step, and 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.

For example, ask your assistant

Every morning, check Datadog monitors that triggered overnight and send me a summary ranked by how long each was in alert.

When a Datadog monitor goes into alert, post the monitor name, value and graph link to Slack.

When a Datadog monitor stays in alert for 15 minutes, open a PagerDuty incident, create a Jira ticket, and post both links to our incidents Slack channel.

Beyond chat

Have Datadog work when you're not in the chat

Connecting Datadog to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Datadog

Datadog needs two keys from your organization: an API key and an application key. Making the Datadog application key owned by a service account, with limited scopes, keeps access tight and independent of any one person.

Datadog

Developer / Observability

  1. In Datadog, open Organization Settings, then API Keys, and create a new key.
  2. Go to Organization Settings, then Application Keys, and create a new key, ideally owned by a service account.
  3. Optionally edit the Datadog application key's scopes to what the automations need, such as monitors_read, slos_read and usage_read.
  4. In the ClickRuntime dashboard, save both keys as secrets on Connections & secrets and choose the Datadog site your organization uses, for example US1 or EU.

Good to know

Datadog limits that affect automations

  • Datadog runs separate sites (US1, US3, US5, EU, AP1 and US1-FED), and keys only work on their own site, so the connection must point at the right one.
  • Reading data needs the Datadog application key as well as the API key.
  • Some endpoints, such as Incidents v2, refuse application keys that have scopes set, so a scoped key may not cover every use.
  • Usage and cost data may need a key with admin-level permissions.
  • Rate limits differ by endpoint, so very frequent checks against a single endpoint can be throttled.

FAQ

Questions about automating Datadog

Why does Datadog need two keys?
The API key identifies your organization and the Datadog application key carries the permissions to read data. Datadog sends both as headers on every request, and reads fail without the Datadog application key.
Can it see monitors in real time instead of once a day?
Yes. Add a webhook mention such as `@webhook-alerts` to a monitor's message and Datadog will call the automation each time that monitor notifies.
What does ClickRuntime read from Datadog?
What your application key's scopes allow. The automations here read monitor status, mutes and downtimes, SLO history and usage summaries; none of them change your monitors.
How is a usage spike detected?
Each day the automation pulls the usage summary, compares it with a stored average and alerts you when ingestion is well above it, for example 30% higher than the weekly norm.
Do I need an AI key for Datadog reports?
No. These reports run on plain numbers and statuses. Should you want a written explanation added, the AI included in every ClickRuntime plan covers it.
Is this a Datadog connector for ChatGPT or Claude?
Not for chatting with Datadog data. A chat connector lets your assistant read and change Datadog while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Datadog event.

Tell your assistant what Datadog should do

Free plan. No credit card.