Webhook
Send alert payloads as HTTP requests to any endpoint — useful for custom integrations, ChatOps bots, ticketing systems, or internal tooling.
| Field | Required | Description |
|---|---|---|
| URL | Yes | Target HTTP endpoint |
| Method | No | HTTP method (defaults to POST) |
| Headers | No | Custom HTTP headers (e.g., Authorization: Bearer <token>) |
| Basic Auth | No | Username / password for HTTP basic authentication |
| Authorization | No | Scheme + credentials for an Authorization header (mutually exclusive with basic auth) |
| Max Alerts | No | Maximum alerts to include in one notification (0 = no limit) |
The payload contains the full alert context including name, status, severity, value, threshold, labels, and annotations.
Payload format
Webhook notifications use the standard Prometheus Alertmanager v4 JSON envelope:
{
"version": "4",
"status": "firing",
"receiver": "my-webhook",
"groupLabels": { "alertname": "HighErrorRate" },
"commonLabels": { "alertname": "HighErrorRate", "severity": "critical" },
"commonAnnotations": { "summary": "…", "description": "…" },
"externalURL": "",
"alerts": [
{
"status": "firing",
"labels": { "alertname": "HighErrorRate", "severity": "critical" },
"annotations": { "summary": "…", "value": "42", "threshold": "10" },
"startsAt": "2026-05-27T00:00:00Z",
"endsAt": "0001-01-01T00:00:00Z",
"generatorURL": "https://<host>/alert-history/…",
"fingerprint": "…"
}
]
}warning: This payload shape is fixed — it's produced by Alertmanager, so the body is not user-templatable. If your receiver requires a different schema (for example a vendor endpoint that validates its own fields), it will reject the request. In that case use a purpose-built channel type (Slack, PagerDuty, Datadog, JSM…) or put a small transformer between KubeSense and the receiver.
Setup
- Create a notification channel of type Webhook and paste the target URL.
- Add any headers or authentication your endpoint requires.
- Click Test to confirm your endpoint accepts the payload (a non-2xx response is reported with the response body, which makes schema mismatches easy to spot).