docs(java): Document Quartz monitor config upsert by wedamija · Pull Request #19777 · getsentry/sentry-docs

wedamija · 2026-10-02T19:41:38Z

DESCRIBE YOUR PR

Adds a "Monitor Config" section to the Quartz integration page. With SentryJobListener.SENTRY_UPSERT_MONITOR_CONFIG_KEY set to "true", SentryJobListener sends a monitor config derived from the job's trigger, so Sentry creates the monitor from code. The section covers how to turn it on, which triggers convert, and what happens to a monitor created in Sentry.

SDK PR: getsentry/sentry-java#6216

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 · 2026-10-02T19:41:42Z

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

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

1 Skipped Deployment

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

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

A JDBC job store with useProperties only accepts String values. Co-Authored-By: Claude <noreply@anthropic.com>

Co-Authored-By: Claude <noreply@anthropic.com>

cursor · 2026-10-05T23:38:48Z

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.

Status	Service	Environment
⚪ Not deployed yet	sentry-docs

Mention @rollout in a comment to update the plan.

Co-Authored-By: Claude <noreply@anthropic.com>

coolguyzone · 2026-10-07T21:12:57Z

+
+## Monitor Config
+
+From the next Sentry Java SDK release (after `8.59.0`), `SentryJobListener` sends a monitor config derived from the job's trigger with each check-in, so Sentry creates the monitor (or updates its schedule) from your code. This is on by default for every job that has a monitor slug.


Suggested change

From the next Sentry Java SDK release (after `8.59.0`), `SentryJobListener` sends a monitor config derived from the job's trigger with each check-in, so Sentry creates the monitor (or updates its schedule) from your code. This is on by default for every job that has a monitor slug.

Starting with Sentry Java SDK 8.59.0, `SentryJobListener` now sends a monitor config derived from the job's trigger with each check-in, so Sentry creates the monitor (or updates its schedule) from your code. This is on by default for every job that has a monitor slug.

coolguyzone · 2026-10-07T21:19:03Z

+- `CronTrigger`: the cron expression and the trigger's time zone. The seconds field must be a fixed number, and the year field, if set, must be `*`.
+- `SimpleTrigger` that repeats forever: the repeat interval, if it's a whole number of minutes.
+
+Other triggers send no monitor config, and neither do triggers with a `Calendar`, jobs with more than one trigger, cron expressions with syntax Sentry doesn't support (such as `15W`, `L-3`, or wrap-around ranges like `FRI-MON`), a step after a day or month name (such as `MON/2`, which Quartz runs every Monday), or time zones that aren't IANA time zone IDs. For these, create the monitor in Sentry first. Whole-hour offsets such as `GMT+2` aren't affected: they're sent as `Etc/GMT-2`.


Suggested change

Other triggers send no monitor config, and neither do triggers with a `Calendar`, jobs with more than one trigger, cron expressions with syntax Sentry doesn't support (such as `15W`, `L-3`, or wrap-around ranges like `FRI-MON`), a step after a day or month name (such as `MON/2`, which Quartz runs every Monday), or time zones that aren't IANA time zone IDs. For these, create the monitor in Sentry first. Whole-hour offsets such as `GMT+2` aren't affected: they're sent as `Etc/GMT-2`.

Monitor configuration isn't sent for any of the following:

- Other trigger types

- Triggers with a `Calendar`

- Jobs with multiple triggers

- Cron expressions that use syntax Sentry doesn't support, such as `15W`, `L-3`, or wraparound ranges like `FRI-MON`

- Cron expressions with a step after a day or month name, such as `MON/2` (which Quartz runs every Monday)

- Time zones that aren't IANA time zone IDs, except for whole-hour offsets such as `GMT+2`, which are sent as `Etc/GMT-2`

In these cases, create the monitor in Sentry first.

coolguyzone

Added a couple suggestions that I think help with clarity, besides that LGTM!

linear-code · 2026-10-21T17:03:43Z

JAVA-9

SentryJobListener sends the trigger's schedule only when sentry-upsert-monitor-config is "true", so existing monitors aren't changed on upgrade.

…itor config

docs(java): Document Quartz monitor config upsert

3052a5d

wedamija mentioned this pull request Oct 2, 2026

feat(quartz): Send monitor config from the trigger with check-ins getsentry/sentry-java#6216

Merged

github-actions Bot added the Priority: Normal Docs review has no urgent deadline label Oct 2, 2026

codeowner-assignment Bot requested a review from a team October 2, 2026 19:42

vercel Bot deployed to Preview – sentry-docs October 2, 2026 19:49

View deployment

docs(java): Make Quartz monitor config upsert opt-in

1f6afe8

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

vercel Bot deployed to Preview – sentry-docs October 2, 2026 20:08

View deployment

docs(java): Note Quartz schedules that send no monitor config

8990e68

vercel Bot deployed to Preview – sentry-docs October 2, 2026 20:53

View deployment

docs(java): Use one job data map and list name steps and calendars

3aa7c09

vercel Bot deployed to Preview – sentry-docs October 3, 2026 00:08

View deployment

docs(java): Set the Quartz upsert key as a String

dd296dd

A JDBC job store with useProperties only accepts String values. Co-Authored-By: Claude <noreply@anthropic.com>

vercel Bot deployed to Preview – sentry-docs October 5, 2026 19:31

View deployment

docs(java): Quartz monitor config is on by default

246eab1

Co-Authored-By: Claude <noreply@anthropic.com>

vercel Bot deployed to Preview – sentry-docs October 5, 2026 23:18

View deployment

wedamija marked this pull request as ready for review October 5, 2026 23:38

wedamija requested review from 0xadam-brown, adinauer, markushi, romtsn and runningcode October 5, 2026 23:38

sentry Bot reviewed Oct 5, 2026

View reviewed changes

Comment thread docs/platforms/java/common/integrations/quartz.mdx Resolved

Comment thread docs/platforms/java/common/integrations/quartz.mdx Resolved

docs(java): Clarify which Quartz time zones send a monitor config

972655b

Co-Authored-By: Claude <noreply@anthropic.com>

vercel Bot deployed to Preview – sentry-docs October 6, 2026 00:51

View deployment

coolguyzone reviewed Oct 7, 2026

View reviewed changes

coolguyzone approved these changes Oct 7, 2026

View reviewed changes

docs(java): Point the monitor config note at releases after 8.60.0

ce64e3b

vercel Bot deployed to Preview – sentry-docs October 13, 2026 19:14

View deployment

wedamija marked this pull request as draft October 23, 2026 21:12

docs(java): Make the Quartz monitor config opt-in

08180f3

SentryJobListener sends the trigger's schedule only when sentry-upsert-monitor-config is "true", so existing monitors aren't changed on upgrade.

vercel Bot deployed to Preview – sentry-docs November 5, 2026 16:52

View deployment

wedamija added 2 commits November 11, 2026 09:23

Merge remote-tracking branch 'origin/master' into q

8f18c57

docs(java): Name 8.64.0 as the first Java SDK version with Quartz mon…

8cfb667

…itor config

wedamija marked this pull request as ready for review November 11, 2026 17:24

vercel Bot deployed to Preview – sentry-docs November 11, 2026 17:33

View deployment

docs(java): List the Quartz triggers that send no monitor config

e6c9eb1

vercel Bot deployed to Preview – sentry-docs November 11, 2026 17:49

View deployment

wedamija merged commit d98d5ea into master Nov 11, 2026
28 checks passed

wedamija deleted the danf/quartz-cron-config-docs branch November 11, 2026 17:52

Navigation Menu

Repository navigation

docs(java): Document Quartz monitor config upsert - #19777

docs(java): Document Quartz monitor config upsert#19777
wedamija merged 12 commits into
masterfrom
danf/quartz-cron-config-docs

wedamija commented Oct 2, 2026 •

edited

Loading

Uh oh!

vercel Bot commented Oct 2, 2026 •

edited

Loading

Uh oh!

cursor Bot commented Oct 5, 2026 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

coolguyzone Oct 7, 2026

Uh oh!

coolguyzone Oct 7, 2026

Uh oh!

coolguyzone left a comment

Uh oh!

linear-code Bot commented Oct 21, 2026

Uh oh!

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants


		## Monitor Config

		From the next Sentry Java SDK release (after `8.59.0`), `SentryJobListener` sends a monitor config derived from the job's trigger with each check-in, so Sentry creates the monitor (or updates its schedule) from your code. This is on by default for every job that has a monitor slug.

	From the next Sentry Java SDK release (after `8.59.0`), `SentryJobListener` sends a monitor config derived from the job's trigger with each check-in, so Sentry creates the monitor (or updates its schedule) from your code. This is on by default for every job that has a monitor slug.
	Starting with Sentry Java SDK 8.59.0, `SentryJobListener` now sends a monitor config derived from the job's trigger with each check-in, so Sentry creates the monitor (or updates its schedule) from your code. This is on by default for every job that has a monitor slug.

-Other triggers send no monitor config, and neither do triggers with a `Calendar`, jobs with more than one trigger, cron expressions with syntax Sentry doesn't support (such as `15W`, `L-3`, or wrap-around ranges like `FRI-MON`), a step after a day or month name (such as `MON/2`, which Quartz runs every Monday), or time zones that aren't IANA time zone IDs. For these, create the monitor in Sentry first. Whole-hour offsets such as `GMT+2` aren't affected: they're sent as `Etc/GMT-2`.
+Monitor configuration isn't sent for any of the following:
+- Other trigger types
+- Triggers with a `Calendar`
+- Jobs with multiple triggers
+- Cron expressions that use syntax Sentry doesn't support, such as `15W`, `L-3`, or wraparound ranges like `FRI-MON`
+- Cron expressions with a step after a day or month name, such as `MON/2` (which Quartz runs every Monday)
+- Time zones that aren't IANA time zone IDs, except for whole-hour offsets such as `GMT+2`, which are sent as `Etc/GMT-2`
+In these cases, create the monitor in Sentry first.

Conversation

wedamija commented Oct 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

DESCRIBE YOUR PR

IS YOUR CHANGE URGENT?

PRE-MERGE CHECKLIST

Uh oh!

vercel Bot commented Oct 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cursor Bot commented Oct 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

coolguyzone Oct 7, 2026

Choose a reason for hiding this comment

Uh oh!

coolguyzone Oct 7, 2026

Choose a reason for hiding this comment

Uh oh!

coolguyzone left a comment

Choose a reason for hiding this comment

Uh oh!

linear-code Bot commented Oct 21, 2026

Uh oh!

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

wedamija commented Oct 2, 2026 •

edited

Loading

vercel Bot commented Oct 2, 2026 •

edited

Loading

cursor Bot commented Oct 5, 2026 •

edited

Loading