Repository navigation
docs(crons): Document monitor config from @Scheduled for Spring @SentryCheckIn - #19780
Merged
Merged
Conversation
…ryCheckIn Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
wedamija
marked this pull request as ready for review
October 5, 2026 23:29
Co-Authored-By: Claude <noreply@anthropic.com>
wedamija
requested review from
0xadam-brown,
adinauer,
markushi,
romtsn and
runningcode
October 5, 2026 23:30
Contributor
|
Services awaiting deployment · Rollout details Warning Rollouts can't watch this change after it deploys: every data source for this team needs to be signed in again, so a check has no telemetry to read. Sign in to your data sources, or ask a team admin to.
Mention |
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
coolguyzone
reviewed
Oct 7, 2026
| </PlatformSection> | ||
| <PlatformSection supported={["java.spring-boot"]}> | ||
| - [Create the monitor in Sentry](https://sentry.io/issues/alerts/new/crons/) first. `@SentryCheckIn` does not send a monitor configuration, so Sentry drops check-ins for a slug that has no monitor. | ||
| - From the next Sentry Java SDK release (after `8.59.0`), `@SentryCheckIn` sends a monitor configuration based on the method's `@Scheduled` annotation by default, and Sentry creates the monitor on the first check-in. With `upsertMonitorConfig = false`, on older SDK versions, or for schedules that can't be converted, [create the monitor in Sentry](https://sentry.io/issues/alerts/new/crons/) first, because Sentry drops check-ins for a slug that has no monitor. |
Contributor
There was a problem hiding this comment.
Suggested change
| - From the next Sentry Java SDK release (after `8.59.0`), `@SentryCheckIn` sends a monitor configuration based on the method's `@Scheduled` annotation by default, and Sentry creates the monitor on the first check-in. With `upsertMonitorConfig = false`, on older SDK versions, or for schedules that can't be converted, [create the monitor in Sentry](https://sentry.io/issues/alerts/new/crons/) first, because Sentry drops check-ins for a slug that has no monitor. | |
| - Starting with Sentry Java SDK 8.59.0, `@SentryCheckIn` now sends a monitor configuration based on the method's `@Scheduled` annotation by default, and Sentry creates the monitor on the first check-in. With `upsertMonitorConfig = false`, on older SDK versions, or for schedules that can't be converted, [create the monitor in Sentry](https://sentry.io/issues/alerts/new/crons/) first, because Sentry drops check-ins for a slug that has no monitor. |
coolguyzone
reviewed
Oct 7, 2026
|
|
||
| ### Monitor Configuration From `@Scheduled` | ||
|
|
||
| From the next Sentry Java SDK release (after `8.59.0`), `@SentryCheckIn` reads the method's `@Scheduled` annotation and sends a monitor configuration with the in-progress check-in by default, so Sentry creates the monitor, or updates its schedule, from your code: |
Contributor
There was a problem hiding this comment.
Suggested change
| From the next Sentry Java SDK release (after `8.59.0`), `@SentryCheckIn` reads the method's `@Scheduled` annotation and sends a monitor configuration with the in-progress check-in by default, so Sentry creates the monitor, or updates its schedule, from your code: | |
| Starting with Sentry Java SDK 8.59.0, , `@SentryCheckIn` now reads the method's `@Scheduled` annotation and sends a monitor configuration with the in-progress check-in by default, so Sentry creates the monitor, or updates its schedule, from your code: |
1 of 3 tasks
wedamija
marked this pull request as draft
October 23, 2026 21:12
@SentryCheckIn sends the schedule only with upsertMonitorConfig = true, so existing monitors aren't changed on upgrade.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
Documents the opt-in
@SentryCheckIn(upsertMonitorConfig = true)attribute for Spring Boot: it sends a monitor config derived from the method's@Scheduled, so Sentry creates the monitor from code. Adds a section on which@Scheduledsettings convert, and narrows "create the monitor in Sentry first" to methods that don't opt in, older SDKs, and schedules that can't be converted.SDK PR: getsentry/sentry-java#6215
IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST