[wedamija]

Part of a series adding automatic Crons monitoring for the most-used job schedulers in each SDK. Check-ins for a monitor that doesn't exist yet are dropped, so today each monitor has to be created by hand with its schedule copied from the code. Sending the job's schedule as the monitor config lets Sentry create the monitor and keep it in sync.

SentryJobListener now sends the trigger's schedule with the in-progress check-in. A CronTrigger is sent as a crontab with its time zone, and a SimpleTrigger that repeats forever as an interval. It's on by default, since adding the listener is already an opt-in to monitoring. On upgrade, existing monitors take their schedule and time zone from the trigger. Setting the sentry-upsert-monitor-config job or trigger data key to "false" turns it off for a job.

JobBuilder.newJob(MyJob.class)
    .usingJobData(SentryJobListener.SENTRY_UPSERT_MONITOR_CONFIG_KEY, "false")

Triggers with a calendar, jobs with several triggers, simple triggers that don't repeat forever and cron syntax Sentry doesn't support check in without a config.

Stacked on #6215.
Docs: getsentry/sentry-docs#19777

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 43e6900

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.59.0 (1)	release

⚙️ sentry-android Build Distribution Settings

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 045b6d8. Configure here.}