[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.

@SentryCheckIn methods now send the schedule from their @Scheduled annotation as the monitor config, so Sentry creates the monitor on the first check-in and updates its schedule when the code changes. It's on by default, since @SentryCheckIn is already an opt-in to monitoring. On upgrade, existing monitors take their schedule and time zone from @Scheduled (the JVM zone when zone isn't set). The change is the same in sentry-spring, sentry-spring-jakarta and sentry-spring-7.

@Scheduled(cron = "0 0 * * * *")
@SentryCheckIn("hourly-sync")
void sync() { ... }

// keep managing the schedule in Sentry
@SentryCheckIn(value = "hourly-sync", upsertMonitorConfig = false)

Fixed-delay schedules and crons Sentry would read differently from Spring check in without a config. Heartbeat check-ins never send one.

Stacked on #6217.
Docs: getsentry/sentry-docs#19780

[github-actions]

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

Generated by 🚫 dangerJS against 5db58a4

[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 6f5ad4e. Configure here.}