Cockpitify Docs Search the docs⌘K Product Sign in Try the live demo

Get instant Sentry alerts for new errors

Updated · Pro and up · Phone · Web

Connect a Sentry internal integration so Cockpitify notifies you within seconds of a new error or a resolved error that comes back.

Instant alerts tell you within seconds when Sentry sees a new error in your app, or when an error you resolved comes back. They’re meant for whoever is on call after a release. Sentry sends each new issue to your project through a webhook; Cockpitify adds the release it was first seen in and notifies you.

Before you start

  • Connect Sentry to the app first. See Release health.
  • You need access to your Sentry organization’s settings to create an integration.

Open instant alerts

  • Phone: open the Product tab, then Release health. Scroll to Instant alerts.
  • Web: open Product → Release health, or App → Connections → Sentry. Find Instant alerts.

The section shows the Webhook URL for this app. You’ll paste it into Sentry.

Set it up in Sentry

It takes about 2 minutes, once.

  1. In Sentry, open Settings → Developer Settings → Custom Integrations → Create New Integration → Internal Integration.
  2. Paste the Webhook URL from Cockpitify as its Webhook URL.
  3. Under Permissions, give Issue & Event “Read”. Under Webhooks, tick issue. Save.
  4. Copy the Client Secret from the integration’s page.
  5. Back in Cockpitify, paste it into Client secret and tap Turn on.

The section then says On since and the date. Once Sentry has sent something, it says when Sentry last reached Cockpitify. Until then it says “Nothing from Sentry yet: it comes with the next new error.”

Choose what alerts you

  • Alert on: Fatal, Error and Warning. Pick at least one. New setups start with Fatal and Error.
  • An error you resolved comes back: what Sentry calls a regression. On by default.

Tap Save after a change. Sentry’s webhook covers your whole organization, but only issues from the Sentry project connected to this app count.

What you get

NotificationWhen
New crash in SentryA new issue at the Fatal level
New error in SentryA new issue at another level you picked
An error came backA resolved issue regressed
More new errorsMore than 3 new issues in 10 minutes

Tap an alert to see the issue, its level, where it happened, the release it was first seen in, the share of devices on that release today and the error count, with Open in Sentry.

When errors pile up, often after a bad release, the first 3 in 10 minutes arrive one by one and the rest come together as one summary. That keeps your phone usable during an incident.

If a delivery from Sentry never arrives, the hourly Sentry reading still picks up new issues as a backup.

Who gets them

Instant alerts are Sentry issue alerts on the Alerts page, shown as “A new Sentry issue or a regression” under Stability. They reach:

Turn it off

Tap Turn off and confirm. Cockpitify forgets the client secret and ignores anything Sentry still sends. You can delete the integration in Sentry too.

If something doesn’t work

  • “That doesn’t look like a client secret (64 characters).” Copy the Client Secret from the integration’s page, not the token.
  • Nothing arrives. Check that the integration’s Webhook URL matches the one in Cockpitify and that issue is ticked under Webhooks. Then check that the error’s level is one you picked.
  • The section says instant alerts need an update. They arrived in ops 0.53.0. Update the project from Connections; your data isn’t touched.
Was this page helpful?YesNo
Ask a question
Questions? Ask me.I’m Murat, the indie developer behind Cockpitify.

I read every message and reply by email, usually within a day.