Integrations

KubeSense supports multiple notification channels for delivering alerts to your team. Configure one or more channels and associate them with alert rules for flexible routing.

Creating a Notification Channel

Navigate to Alerts in the sidebar and open the notification channel settings. Click to add a new channel.

After selecting a type, provide the required configuration fields (see below), then save the channel.

---

Supported Channels

Slack

Send alert notifications to a Slack channel via an incoming webhook.

Slack messages include alert name, status (firing/resolved), severity, value, threshold, description, labels, and a link to open the alert in KubeSense. When multiple alerts are batched, the title shows firing and resolved counts (e.g., [FIRING:6, RESOLVED:1] Logs Availability).

Microsoft Teams

Send alert notifications to a Microsoft Teams channel via a webhook connector.

Teams messages use Adaptive Card formatting with the same information as Slack — alert name, status, severity, value, threshold, labels, and timestamps.

Email

Deliver alert notifications via SMTP email to one or more recipients.

PagerDuty

Create incidents in PagerDuty when alerts fire, and auto-resolve when alerts recover.

Alert severity is mapped to PagerDuty severity levels. Resolved alerts automatically resolve the corresponding PagerDuty incident.

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.

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

Google Chat

Send alert notifications to a Google Chat space via an incoming webhook.

Google Chat messages use Cards v2 format with alert name, status, severity, description, value, threshold, and labels.

Webhook

Send alert payloads as HTTP requests to any endpoint — useful for custom integrations, ChatOps bots, ticketing systems, or internal tooling.

The payload contains the full alert context including name, status, severity, value, threshold, labels, and annotations.

---

Alert Routing

There are two ways to route alerts to notification channels:

Direct Assignment

When creating an alert rule, select a specific notification channel from the Notification Channel dropdown in the Alert Routing section. All alerts from that rule are sent to the selected channel.

Label-Based Routing (Notification Channel Policy)

Configure Matching Labels on a notification channel to enable automatic routing. When an alert fires, its labels are compared against the matching labels of all channels. If a channel's matchers match the alert's labels, that channel receives the notification.

This enables patterns like:

• Channel with severity = critical receives all critical alerts
• Channel with team = platform receives all alerts labeled for the platform team
• Channel with no matchers acts as a catch-all for unmatched alerts

Multiple channels can match a single alert, allowing you to send the same alert to both Slack and PagerDuty simultaneously.

---

Testing Channels

After creating a notification channel, use the Test action to send a test notification and verify connectivity before associating it with alert rules.

---

Notification Content

All notification channels receive the same core alert information:

For batched notifications (multiple alerts grouped together), the title includes firing and resolved counts — for example, [FIRING:6, RESOLVED:1] Logs Availability.