Klaxon

Dashboard

Live incident status and on-call coverage

Active Incidents

On Call Now

Incidents

Alerts that created an incident

Title	Severity	Status	Created

On Call

Current on-call engineer per schedule

Teams

Organisational units for schedules and policies

Name	Slug	Team ID	Created

Schedules

On-call rotations with DST-aware handoffs

Name	Team	Timezone	ID

Escalation Policies

Step-by-step alert escalation rules

Name	Team	Steps	Repeat

Service Catalog

Software components and their operational status

Service	Team	Status	Description

Integrations

Webhook endpoints for each monitoring source

Name	Type	Ingest URL

Users

On-call engineers and their notification preferences

Name	Email	Timezone	Status	User ID

Routes

Alert routing rules to escalation policies

Name	Team	Matcher	Priority

Heartbeats

Dead man's switch monitors for scheduled jobs

Name	Slug	Status	Interval	Grace	Last Seen

Silences

Suppress alerts during maintenance windows

Matchers	Starts	Ends	Created By	Comment

Analytics

Incident trends, MTTR/MTTA, and notification delivery

Incidents per Day

By Severity

On-Call Load

Notification Delivery

Audit Log

All administrative actions

Time	Action	Resource	ID	Actor	Details

Settings

Server-wide configuration

Server

External URL

Used in notification links and webhook callbacks.

Email / SMTP

Shared SMTP server used by all email contact methods. Per-contact provider_ref JSON overrides these values.

SMTP Host

SMTP Port

SMTP Username

SMTP Password

From Address

One bot serves the whole org. Create a bot via @BotFather, paste the token here, then each user only needs to set their Chat ID as the contact address.

Bot Token

Users set their Chat ID as the contact address. Get it from @userinfobot.

Pushover

Create an Application at pushover.net/apps/build. The Application Token is shared org-wide; each user provides their own User Key as the contact address.

Application Token

Users set their Pushover User Key as the contact address.

ntfy

ntfy is a simple push notification service. Leave Server blank to use the public ntfy.sh. For self-hosted ntfy, enter your server URL. Users set their topic name (or full URL) as the contact address.

Server URL

Leave blank to use ntfy.sh.

Auth Token

Optional. Required if your ntfy server enforces authentication.

Slack

Slack uses per-channel Incoming Webhooks — there is no shared admin token. Each user contact method needs its own webhook URL.

Per-user setup

Go to api.slack.com/apps → New App → From Scratch
Enable Incoming Webhooks and add to a workspace
Copy the Webhook URL
Add a Slack contact method to the user with that URL as the address
Optionally add {"channel":"#override","username":"Klaxon"} as Config JSON

Discord

Discord uses per-channel Incoming Webhooks — no shared org token required.

Per-user setup

In Discord, open a channel → Edit Channel → Integrations → Webhooks
Create a webhook and copy the URL
Add a Discord contact method to the user with that URL as the address

Microsoft Teams

Teams uses per-channel Incoming Webhooks connectors — no shared admin token required.

Per-user setup

In Teams, open a channel → … → Connectors → Incoming Webhook
Configure and copy the webhook URL
Add a Teams contact method to the user with that URL as the address

PagerDuty

Klaxon sends events to PagerDuty via the Events API v2. Each service has its own Integration/Routing Key — set it as the contact method address.

Per-user setup

In PagerDuty, go to a Service → Integrations → Add Integration → Events API v2
Copy the Integration Key
Add a PagerDuty contact method to the user with the Integration Key as the address

Generic Webhook

Klaxon POSTs a JSON incident payload to any HTTP endpoint. Each contact method has its own URL.

Payload structure

{"incident_id":"...","title":"...","severity":"critical",
"status":"triggered","labels":{},"created_at":"..."}

Per-user setup

Add a Webhook contact method with your endpoint URL as the address. Optionally add {"secret":"..."} as Config JSON — Klaxon will send it as X-Klaxon-Secret.

API Tokens (RBAC)

Scoped tokens for CI, scripts, and integrations. Roles: admin (full) · operator (incidents + config) · responder (ack/resolve) · viewer (read-only).

Description

Role