Smart Alerting

skopos.app/alerts — Active Rules

4 rules · 3 active · 1 paused

High error rateERROR● activeemail

≥ 10 ERROR events in 60s→ops@company.com

Auth service warningsWARN● activeslack

≥ 50 WARN events in 300s→#alerts

Critical payment failuresERROR● activeemail

≥ 3 ERROR events in 60s→oncall@company.com

API gateway anomaliesERROR○ pausedslack

≥ 20 ERROR events in 120s→#api-team

Recently fired alerts

last 24h

Critical payment failures1 min agopayment-svc

28 ERROR events in last 60s — threshold was 3

email → oncall@company.com·✓ delivered

High error rate47 min agouser-service

14 ERROR events in last 60s — threshold was 10 (db pool exhausted)

slack → #incidents·✓ delivered

Auth service warnings3 hr agoauth-service

67 WARN events in last 5m — threshold was 50 (jwt clock skew)

slack → #alerts·✓ delivered

Built for on-call sanity

—

Route any rule to email addresses or Slack webhooks. Different rules can go to different channels — ops, oncall, frontend, whatever fits your team.

—

Fire only when N events of a given level happen within a time window. No more pages for transient blips.

—

60 seconds for critical paths, 5 minutes for warnings, 1 hour for trends. You set what matters.

—

Scope alerts to specific services with one filter. Stop the auth-service spam from drowning out your payments alerts.

—

Once an alert fires, it won't fire again for the same pattern in the same window. Quiet inboxes, signal-rich pages.

—

Every fired alert is logged with timestamp, payload, and delivery status. Replay history during postmortems.