Skip to content

Commit 150a81e

Browse files
feat(crons): Add note on consecutive failure alerts (#6078)
Co-authored-by: Liza Mock <liza.mock@sentry.io>
1 parent ac6bda4 commit 150a81e

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

src/docs/product/crons/alerts.mdx

+6
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,12 @@ When your recurring job fails to check-in on schedule or runs beyond its configu
1111

1212
Navigate to the alerts tab in Sentry and create a new issue alert. You should see the issue alert builder. From here, you can start configuring your cron monitor alert rule. First, select the project corresponding to your cron monitor. Then, in the `IF` section of the alert rule configuration, add a new filter. You'll want to select the filter labeled "The event's tags match {key} {match} {value}".
1313

14+
<Note>
15+
16+
You can use the "Number of events in an issue is" trigger filter to only alert you if the monitor has failed multiple consecutive check-ins. For example, if your job is supposed to run every minute, you could use the trigger filter **Number of events in an issue is more than 10 in 15 minutes**, to be alerted only after it's failed more than 10 times in that timeframe.
17+
18+
</Note>
19+
1420
![Cron alert filter](cron-alert-filter.png)
1521

1622
Fill in the `key` text field with `monitor.id`, then have it `equal` the id of the cron monitor that you'd like to be alerted on. You'll see your cron monitor's id in the cron monitor's detail page.

0 commit comments

Comments
 (0)