Skip to content
Alerting

The right alert to the right person

Escalation paths decide who hears about what: notify a channel, wait, page whoever is on call, branch on severity or working hours. Acknowledge once and the escalation stops.

9 channel types
From email and Slack to SMS and phone calls.
Branches and working hours
Split a path on severity, time of day, source or labels.
Your other tools too
Grafana, Alertmanager, Sentry, webhooks and email.
Escalation paths

Escalation paths you can read at a glance

Notify a channel, wait, page whoever is on call, open an incident. Branch on severity, working hours, source or labels, and acknowledge once to stop it all.

  • Wait a fixed time or until working hours begin
  • Acknowledge to stop the escalation
  • Multiple paths on Team and Business, one on Starter
  1. Kestrel
  2. Alerting
  3. Database escalation
Add stepNotifyOn-callIncidentBranch
Trigger
Alert fired
Alert enters this path
Step 1 · Notify+0m
#ops-alerts
Slack
Branch
  • Ifwithin working hours
  • orseverity is critical
Yes
Step 2 · On-call+0m
Database on-call
Now: Priya Raman
No
Step 3 · On-call09:00
Database on-call
Waits for 09:00
Step 4 · Incident+15m
Create incident
If still firing
Channels

Alerts where your team already is

Email, Slack, Microsoft Teams, Discord, Telegram, Pushover, webhooks, SMS and phone calls. Messages update in place when an alert is acknowledged or resolved.

  • Acknowledge from Slack, Telegram or a phone call
  • Response time and metric charts in the alert
  • SMS and voice credits included every month
  1. Kestrel
  2. Alerting
Channels

Destinations your paths notify. Send a test to check delivery.

Enabled
#ops-alerts
Slack
Used in 2 pathsSend test
Enabled
On-call phones
Phone call
Used in 2 pathsSend test
Enabled
Ops email
Email
Used in 2 pathsSend test
Enabled
Kestrel ops
Telegram
Used in 1 pathSend test
Enabled
Pager SMS
SMS
Used in 1 pathSend test
Auto-disabled
Incident webhook
Webhook
Stopped after repeated failuresTest & re-enable
Alert sources

One place for alerts from your other tools

Connect Grafana, Prometheus Alertmanager, Sentry, any webhook or plain email. Repeats keep one alert firing, and a resolve from the tool resolves it.

  • Duplicates collapse into one firing alert
  • Resolves when the tool says it's resolved
  • Last 7 days of raw requests for debugging
  1. Kestrel
  2. Alerting
  3. Sources
  4. Grafana
G
Grafana
Receiving
Firing now
1
External alerts
Last received
2m ago
Default severity
High
Resolved by the tool

Recent events

Everything this source received in the last 7 days.

  • firedHigh error rate on checkout-api2m ago
  • resolvedPostgresReplicationLag on db-fra-248m ago
  • still firingHigh error rate on checkout-api1h ago
  • firedDisk will fill in 4h on fra-db-013h ago
  • testTest alert sent from Spectate1d ago
In detail

Everything in alerting

Alert mails that explain

The cause in plain words, and what to check first.

Failing channels switch off

Escalations skip them and owners get an email.

Test any channel

A successful test re-enables a disabled channel.

Severity mapping

P1, fatal or warning from your tools, mapped for you.

Escalation log

Every step and branch decision on the alert's timeline.

Paths are snapshotted

Edits never disturb a running escalation.

Included on every plan. See pricing

FAQ

Alerting: questions

Which notification channels does Spectate support?

Email, Slack, Microsoft Teams, Discord, Telegram, Pushover, webhooks, SMS and phone calls. Every channel type is available on every plan. SMS and phone calls use credits: every plan includes a monthly allowance of 10, 50 or 200 credits, and packs of 100 cost €19 and never expire.

What is an escalation path?

A set of steps that runs when an alert fires: notify channels, wait, page whoever is on call, open an incident. Branches send alerts down different sides based on severity, working hours, the source or labels. The escalation stops as soon as someone acknowledges the alert, and steps that can't deliver are skipped.

Can I alert differently during and outside working hours?

Yes. Each escalation path has working hours with days, times and a time zone. A branch can check whether an alert arrives within or outside them, and a wait step can hold an alert until working hours begin, for example to page at night only for critical alerts and wait until morning for the rest.

Can Spectate receive alerts from Grafana, Prometheus or Sentry?

Yes. Add an alert source for Grafana, Prometheus Alertmanager, Sentry, a generic webhook or email. Spectate turns each request into an alert with a severity, routes it through your escalation paths and resolves it when the tool reports recovery. Repeated notifications for the same problem keep one alert firing.

How do I acknowledge an alert?

From the dashboard, with the Acknowledge button in Slack or Telegram, or by pressing 1 when Spectate calls you. Acknowledging stops the escalation, and Slack and Telegram messages update to show who acknowledged it and when. Any team member can acknowledge.

What happens if a notification channel stops working?

Spectate counts failed deliveries per channel. After 5 failures in a row, 2 permanent errors such as a revoked token, or 24 hours of failures, the channel is disabled and owners and admins get an email. Escalations skip it and continue with the next step, and a successful test re-enables it.

Do I need the Team plan for escalation paths?

Starter includes one escalation path, the team default, with every channel type. Team and Business add as many paths as you need and on-call steps that page whoever is on call. Team costs €0.60 per monitor a month with a minimum of 80 monitors.

Know about it first.

Set up your first monitor in under a minute. 14 days free, no credit card.