Skip to main content

​
Before you start

  • The Sentry email, or a Sentry login and the backend project’s issue list.
  • Monitor checks open beside you; it maps each issue title to its check.

​
Steps

1

Open the issue, not the digest

Sentry may bundle several alerts into one digest email. Follow the link to each issue inside it. Everything below is read from the issue page.
2

Tell the two kinds apart

An uptime incident comes from the uptime check named Comfort Hub technician access and monitoring and is about the engine’s front door, not a record. It has no check tag. Stop here and follow Check the monitor is running.A business condition has a plain sentence as its title, a check tag naming the check, a disposition tag saying urgent or review, and an occurrence tag saying which spell this is.
3

Read the four parts

The title is the summary: what is wrong. Under Additional Data are the resource (the record, as an id), the action (what the check suggests you do) and the evidence (the ids and counts that locate the problem). Evidence never carries customer content, only identifiers.
4

Find the check

Match the title to its row on Monitor checks. The row tells you how often the check runs, which decides how soon the issue can close once you have fixed the cause.
5

Fix the cause where the record lives

Put the record right in the system that owns it; Who is the source of truth says which. The usual routes:
6

Leave the issue open

Do not click Resolve. The monitor resolves the issue itself when the check next runs and no longer sees the problem. An issue resolved by hand looks fixed in Sentry while the condition stays open in the engine, and nothing brings it back to your attention.

​
How you know it worked

  • The issue shows as resolved with no person’s name on the resolution; the monitor resolved it through Sentry’s API.
  • For a check that runs every minute, that happens within a minute or two of the fix. For the others, at the check’s next run.
  • If the same problem returns later, it opens as a new issue with the next spell number, and you get a new email.

​
If it did not work

  • The check has not run yet. Slow checks run every 5 or 15 minutes, hourly or nightly; the schedule is on Monitor checks.
  • The fix is on the wrong side. Checks read the engine’s copy of the record. A fix made in Zoho or QuickBooks reaches the engine through sync; if it did not, see Fix a record that did not sync.
  • The title says the check exceeded its capacity. More than 500 records match. The check reports the first 500 and cannot declare recovery for the rest, so the capacity issue stays until fewer than 500 remain.
  • The issue came back. The cause was not fixed, only the symptom. Read the evidence again.