Feature

One event, accountable delivery

Notifications that reach the right responder.

PageLantern routes failures, threshold breaches, expiry warnings, and recoveries through workspace defaults and monitor-specific policies, then keeps a delivery trail for follow-up.

Configure alertsRead the channel guide
Monitoring events flowing through an alert-routing hub to email, chat, webhook, SMS, and paging destinations.
Operational flow: event, routing policy, delivery channel, and history.

Event matched

A failure, recovery, expiry warning, or missed heartbeat activates the applicable policy.

Signal

Destination selected

Workspace defaults or a monitor-specific override determine where it goes.

Routed

Delivery recorded

Notification history preserves the attempt for audit and triage.

Recorded

Channels and policy

Reach responders without losing the delivery trail.

Use shared defaults for broad coverage, then override the route when a critical monitor needs a different responder or channel.

Delivery channels

Use the destinations teams already watch.

  • Email and metered SMS
  • Slack, Microsoft Teams, and Discord
  • Webhooks and PagerDuty

Routing evidence

Know which policy and destination applied.

  • Workspace notification defaults
  • Monitor-specific overrides
  • Delivery and recovery history

Plan limits: Free includes 1 counted alert channel, Starter 5, and Team unlimited. SMS is separate: 50 messages a month on Starter and 200 on Team.

Example delivery

A route responders can reconstruct later.

Illustrative values show the event, applied policy, destinations, and recovery window.

Event
API latency threshold
Policy
Payments override
Destinations
PagerDuty + Slack
Opened
02:14 UTC
Recovery
02:22 UTC
Outcome
Delivery recorded

Next step

Route the next alert before it matters.

Start freeSee plans

FAQ

Frequently asked questions

Which alert channels does PageLantern support?

Alerts can route to email, Slack, Microsoft Teams, Discord, webhooks, and PagerDuty, and recovery notices tell responders when a service returns to healthy.

Can I set different alert routing per monitor?

Yes. You define workspace notification defaults, then override destinations, thresholds, and expiry alerts for critical or customer-specific monitors.

Can I see who was notified after an incident?

Yes. Delivery history is tied to monitors and incidents, so you can reconstruct who was notified and when during a post-incident review.