MonSPHERE

Alerting & Incidents

Alert Management

Threshold and anomaly-based alert rules, routed through Alertmanager to your team.

Alert rules evaluate metrics or monitor status against conditions you define, and route matches through Alertmanager into MonSPHERE's own alert-engine.

Creating an alert rule

curl -X POST https://api.monsphere.com/api/v1/organizations/:orgId/alert-rules \
  -H "X-Api-Key: msk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "name": "High CPU",
    "monitorId": "...",
    "condition": "cpu_usage > 90",
    "forMinutes": 5,
    "severity": "warning"
  }'

Routing

Alert rules attach to notification channels — Slack, Microsoft Teams, Discord, Telegram, PagerDuty, Opsgenie, a custom Webhook, or Email. See Integrations for the full, honestly-labeled list of what's implemented today.

Deduplication and grouping

Because alert evaluation sits on real Alertmanager, you get proper grouping and deduplication — a flapping condition doesn't spam ten separate notifications, it groups into one that updates.

From alert to incident

A firing alert rule creates an event on the internal event bus (SubjectAlertReceived); incident-service consumes it and opens a tracked incident automatically — see Incident Management.