Sentry integration

Escalate Sentry issues to phone calls, Telegram and on-call

Use Sentry's webhook integration to route only the issues that matter. Filter by environment, level or release tag — the rest stays in your chat channels.

Start free View API examples
Setup
Internal app
Filter
By tags
Release context
Preserved

Anatomy of a Sentry issue

LIVE
Sentry → alert rule
ChargeFailedException, env=prod
WardenPoint
filter by tags · escalate · acknowledge
Telegram
Voice call
Email

Setup

Wire Sentry to WardenPoint via webhook

Sentry offers an Internal Integration that posts a webhook to any URL. Three clicks and you're routing critical issues to on-call.

  1. 1Step 1

    Create an internal integration

    In Sentry: Settings → Custom Integrations → Create New Integration. Name it WardenPoint and add the webhook URL.

    $ Settings › Custom Integrations › Create
  2. 2Step 2

    Set the alert webhook URL

    Paste the WardenPoint URL into the Webhook URL field. Tick 'Issue Alerts' under Webhooks scope.

    $ Webhook URL › https://api.wardenpoint.com/hooks/…
  3. 3Step 3

    Configure an alert rule

    Alerts → Create Alert Rule. Pick conditions (level = error, environment = production), pick Action 'Send a notification via WardenPoint'.

    $ Alerts › Create Alert Rule

Wire format

What Sentry sends on an issue alert

Sentry posts an action payload with the issue, level, project and tags. WardenPoint reads release and environment tags so the on-call sees the deploy context.

Sentry → WardenPoint
sentry-action.jsonJSON
{
"action": "triggered",
"data": {
"issue": {
"id": "1234567",
"title": "Stripe::ChargeFailedException",
"level": "error",
"environment": "production",
"project": "api",
"tags": [["release", "[email protected]"]]
}
}
}
WardenPoint fan-out
WardenPoint response202
{
"status": "queued",
"notification_uuid": "notif_8h2k7yQrxJp",
"channels_planned": [
"telegram_voice",
"voice_call",
"email"
],
"escalation_chain_id": "esc_4j2k9bMcvL"
}

Routing recipes

Three Sentry patterns to avoid alert fatigue

Sentry creates lots of events. Use alert rules to send only the ones that need a human now.

Level

Errors only — drop warnings

Match level=error in the alert rule. Warnings stay in Slack; errors page on-call via WardenPoint.

match
level: error
→ route
priority: critical
Environment

Production only

Add environment=production to the rule. Staging issues never wake anyone up.

match
environment: production
→ route
policy: prod_oncall
Release

Recent release window

Combine with 'event.frequency >= 5 in 10 min' to suppress slow drips and only escalate spikes.

match
release: api@*
→ route
burst-only

Sentry FAQ

Common Sentry integration questions

Yes. When Sentry marks the issue resolved (manually or via the Resolved-in-next-release flow), it fires a resolved hook and WardenPoint cancels the escalation chain.
Free plan

Escalate only the Sentry issues that matter

Start on the free plan, wire one alert rule for production errors and see how a tag-filtered escalation feels.

Start free Back to integrations
  • Tag-filtered alerts
  • Resolve hook respected
  • Release context in payload