Skip to main content

Datadog Alerts Integration

Overview​

Configure Datadog monitors to send alert notifications to OpsWorker for automatic investigation.

Prerequisites​

  • A Datadog account with monitor configuration access
  • OpsWorker cluster set up with the Kubernetes Agent installed
  • Your OpsWorker webhook URL (available in the portal under Integrations → Datadog)

Setup​

1. Get Your Webhook URL​

  1. In the OpsWorker portal, go to Integrations
  2. Select your cluster
  3. Find Datadog and copy the webhook URL

2. Create a Webhook in Datadog​

  1. In Datadog, go to Integrations → Webhooks
  2. Click New Webhook
  3. Configure:
    • Name: opsworker
    • URL: Your OpsWorker webhook URL
    • Payload: Leave as default (OpsWorker accepts the standard Datadog webhook format)
  4. Click Save

3. Add Webhook to Monitors​

For each monitor you want OpsWorker to investigate:

  1. Edit the monitor
  2. In the Notify your team section, add: @webhook-opsworker
  3. Save the monitor

Alternatively, add @webhook-opsworker to a monitor template to apply it to multiple monitors at once.

4. Verify​

Trigger a test alert from one of your configured monitors. Check the OpsWorker portal under Alerts to verify signals are arriving.

Adding Query Capabilities​

The Datadog webhook covers alert ingestion only. To let OpsWorker run metric and log queries during investigations, configure the Grafana MCP integration — Grafana can sit in front of Datadog datasources and expose them via PromQL/LogQL for OpsWorker.

Supported Monitor Types​

OpsWorker can investigate alerts from these Datadog monitor types:

  • Metric monitors
  • APM monitors
  • Log monitors
  • Process monitors
  • Composite monitors

For best investigation quality, ensure monitors include Kubernetes context tags (kube_namespace, pod_name, deployment) so OpsWorker can map the alert to a resource.

Next Steps​