Datadog On-Call

Page a Datadog On-Call team directly from KubeSense alerts. Uses the Datadog On-Call paging API — no native integration required on the Datadog side, and works for any region (US, EU, US3, US5, AP1) or private Datadog deployment.

Prerequisites

Set up the following in Datadog before creating the KubeSense channel:

1. API Key — Navigate to Organization Settings → API Keys. Create a new key or copy an existing one. This is the DD-API-KEY.
2. Application Key with on_call_page scope — Navigate to Organization Settings → Application Keys. Create a new key and make sure the on_call_page permission is granted. This is the DD-APPLICATION-KEY. Without this scope the paging API returns 403 Forbidden.
3. On-Call Team — Navigate to On-Call → Teams and click Set Up Team. Configure:
   • Team members
   • Escalation policy
   • Schedules
   • Notification methods (SMS, push, email) for each team member
4. Team Handle — Note the team handle from the team page (e.g. product-autopay). This is the identifier used to page the team.

Channel Configuration

Region API URLs:

For private or proxied Datadog deployments, paste the base URL pointing to your tenant.

Routing to multiple teams

Unlike Jira Service Management — where the team is baked into the API integration key — Datadog carries the team as an explicit Team Handle field, so one API key + Application key pair can page any number of teams:

1. Reuse the same API Key and Application Key across channels.
2. Create one channel per team, changing only the Team Handle (e.g. product-autopay, platform-infra).
3. Send alerts to the right team by selecting the channel on the alert rule, or with Matching Labels on the channel (e.g. team = payments). See Alert Routing.

Only the credentials are shared — each channel still gets its own receiver, urgency, and routing.

Per-Alert Urgency Override

To override the channel's default urgency on a per-rule basis, add an urgency label to the alert rule with value high or low. The first alert in a group with this label sets the urgency for the entire page.

Notification Content

Each page sent to Datadog includes:

• Title — <alertname> [FIRING:N, RESOLVED:M]
• Description — Multi-line summary with status, severity, summary, description, Alertmanager URL, and per-alert details (name, value, threshold, labels, start time). Truncated after the first 5 alerts.
• Tags — source:kubesense, severity:<level>, alertname:<name>, and env:<value> when present.
• Target — The team handle configured on the channel.

Pages appear in Datadog → On-Call → Pages and follow the team's escalation policy.

Common Errors