docs(crons): Document monitor config from @Scheduled for Spring @SentryCheckIn

[wedamija]

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 @Scheduled settings 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

Merge after the SDK release, and replace "the next Sentry Java SDK release (after 8.59.0)" with the released version.

IS YOUR CHANGE URGENT?

• Urgent deadline (GA date, etc.): YYYY-MM-DD
• Other deadline: YYYY-MM-DD
• No deadline: Not urgent, can wait up to 1 week+

PRE-MERGE CHECKLIST

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-docs	Ready	Preview	Oct 5, 2026 11:38pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
develop-docs	Ignored	Preview	Oct 5, 2026 11:38pm UTC

[cursor]

The change documents how a scheduled job can send monitor config from code. Watch page errors, request success, and sibling cron-page traffic. An issue escalates when page errors appear or request success drops.

Services: sentry-docs.

Mention @change-monitor in a comment to update the plan.

Plan

What changed

The Spring Boot cron page now says check-in can send monitor config from the scheduled annotation. Sentry then creates or updates the monitor on the first check-in. Readers still create the monitor in Sentry first for older SDKs, opted-out methods, and schedules that cannot convert.

This change is live after sentry-docs deploys. It does not ship develop-docs or sentry-changelog.

Risk

Wrong MDX can ship a blank or broken cron setup page. A bad code fence can throw in the shared code-tab client. The same include also feeds the plain Java cron page.

Intended effect

This is a docs edit. Telemetry cannot show the new wording. There is no queryable intended-effect signal.

Absent would mean the live page still says to create the monitor in Sentry first. It would also lack the new schedule section.

Regression watch

Broken MDX or a bad code fence would show as errors or failed fetches on the changed page. The same include can also break the sibling Java cron page. Shared code-tab failures can raise site-wide client errors.

Traces sample at 30 percent. Volume on this path is low. A short drop can be noise.

Signal	Baseline	Window	Source	Rule
Error events on /platforms/java/guides/spring-boot/crons/	0 events	2026-10-04T23:31:08Z to 2026-10-05T23:31:08Z	Sentry errors, project docs, environment:production url:*spring-boot/crons*	Hold at zero. Any rise is a regression.
HTTP success for that URL	53 of 53 spans were status 200 and ok (100%)	2026-10-04T23:31:08Z to 2026-10-05T23:31:08Z	Sentry traces, http.method:GET http.url:*docs.sentry.io/platforms/java/guides/spring-boot/crons* environment:production grouped by http.status_code and span.status	Hold at 100% 200/ok. Any non-200 is a regression.
Client GET volume for that URL, transaction /:path*?	47 spans in 24h. 427 spans in 7d, about 61 per day. Band 47-61 per day	24h: 2026-10-04T23:31:08Z to 2026-10-05T23:31:08Z. 7d: 2026-09-28T23:31:08Z to 2026-10-05T23:31:08Z	Sentry traces, environment:production http.method:GET (http.url:*/platforms/java/guides/spring-boot/crons* OR http.target:*/platforms/java/guides/spring-boot/crons*) grouped by transaction	Hold in the 47-61 per day band. Escalate if volume stays at zero while other docs traffic continues.
Sibling Java cron GET volume, transaction /:path*?	43 spans in 24h. Server GET docs.sentry.io was 10 spans, p95 607ms	2026-10-04T23:31:08Z to 2026-10-05T23:31:08Z	Sentry traces, environment:production http.method:GET (http.url:*/platforms/java/crons* OR http.target:*/platforms/java/crons*) !http.url:*spring-boot* !http.target:*spring-boot* grouped by transaction	Escalate if this volume stays at zero while other docs traffic continues.
Docs production error events	1-18 events per hour. 138 events in 24h. Peak 18 at 2026-10-05T12:00Z	2026-10-04T23:31:08Z to 2026-10-05T23:31:08Z	Sentry errors, project docs, environment:production count per hour	Hold in the 1-18 events per hour band. Escalate if hourly count stays above 18.

If page errors rise, inspect code-tab and platform-selector client errors on that URL.

Not observable

Sentry cannot read whether the live HTML contains the new heading. This plan cannot check whether the conversion table matches SDK behavior. Pageload and navigation spans for this URL returned no rows in the 24h window.