[michaelmairegger]

Changelog Entry

• Add Sentry.Quartz, an integration for Quartz.NET 4.x
  • services.AddQuartz(q => q.AddSentry()) runs each job in its own scope and trace, tagged with its job key, and captures the exceptions jobs throw
  • Jobs marked with [SentryMonitorSlug] send a Sentry Crons check-in for every run, with the trigger's cron or interval schedule as the monitor config, so monitors are created and kept up to date automatically
  • SentryQuartzOptions.ConfigureMonitorOptions customizes thresholds or the schedule, and SendMonitorConfig = false sends check-ins without a schedule

Description

Adds Sentry.Quartz, a Quartz.NET 4.x integration built on Quartz's job middleware.

services.AddQuartz(q => q.AddSentry());

[SentryMonitorSlug] // or [SentryMonitorSlug("nightly-report")]
public class NightlyReport : IJob { ... }

Each job runs in its own Sentry scope and trace (unless global mode is enabled), tagged quartz.job with its job key, and what it throws is captured in that scope. Quartz's ErrorLogger logs the same exception again, wrapped in a JobExecutionProcessException, which the SDK's default deduplication doesn't catch. So with Sentry's logging integration on, a log entry filter drops that entry, and each failure is captured once. Jobs with [SentryMonitorSlug] also send a check-in for each run: in progress when it starts, then ok or error with its duration. A cancelled run counts as an error.

The monitor slug is the attribute's value, otherwise the slugified job key (reports.DailyEmail becomes reports-dailyemail). A SentryMonitorSlug entry in the job's or trigger's data map overrides both.

The in-progress check-in carries the trigger's schedule as the monitor config, so monitors don't have to be created by hand. A schedule is only sent when Sentry reads it the same way Quartz does: cron triggers with a fixed seconds field, no year and no L/W/#, and simple triggers that repeat forever at whole minutes, hours or days. Triggers with a calendar, and triggers that share a monitor slug but have different schedules, get check-ins without a schedule rather than one that would raise false missed check-in alerts. To spot shared slugs, the SDK reads every monitored trigger in the scheduler and reuses the result for a minute.

Quartz 4 only targets net10.0, so this package does too. Quartz 3 support is in #5668, which compiles the same Core/ files against Quartz 3. The only change to Sentry itself is an internal SentryMonitorOptions.HasSchedule and CopyTo, which let ConfigureMonitorOptions replace the trigger's schedule. The filter needs SentryLoggingOptions, so Sentry.Quartz depends on Sentry.Extensions.Logging. Dropping the duplicate with an exception filter in Sentry instead would avoid that dependency, but each dropped event would then show up as discarded in client reports. There's a sample in samples/Sentry.Samples.Quartz.

Docs are in getsentry/sentry-docs#19790. .craft.yml points mainDocsUrl at the page that PR adds, so it should be merged before this is released.

Closes #4601

🤖 Generated with Claude Code

[michaelmairegger]

@jamescrosswell I will continue watching Quartz.Net alpha releases and adopt it until final bits of 4.0 will be released.
I will notify you when ready.

[jamescrosswell]

@jamescrosswell I will continue watching Quartz.Net alpha releases and adopt it until final bits of 4.0 will be released. I will notify you when ready.

Fantastic, thank you @michaelmairegger !

Maybe we mark the PR as draft until then? That let's me know it doesn't yet need my attention (you can always tag me directly if you want my input on something before v4 is released).

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Stale Bugbot comment from a previous run.

[michaelmairegger]

@jamescrosswell quartz.net released final bits of v4. I updated the package to the final version and would say this first version of the package is feature complete.

[jamescrosswell]

@jamescrosswell quartz.net released final bits of v4. I updated the package to the final version and would say this first version of the package is feature complete.

Nice - thanks @michaelmairegger. I wasn't expecting them to get v4 out so quickly!

Apologies in advance... I might be a bis slow on reviewing - there's quite a but going on right now and the invention of AI has made it much easier for people to make PRs - so I'm spread a bit thin.

[codecov]

Codecov Report

❌ Patch coverage is 91.56977% with 29 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.12%. Comparing base (876f7a6) to head (f3d7c36).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
src/Sentry.Quartz/Core/JobMonitor.cs	89.61%	8 Missing and 8 partials ⚠️
src/Sentry.Quartz/Core/TriggerSchedule.cs	92.59%	3 Missing and 5 partials ⚠️
src/Sentry.Quartz/SentryQuartzBuilderExtensions.cs	62.50%	3 Missing ⚠️
src/Sentry.Quartz/QuartzApi.cs	88.23%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5505      +/-   ##
==========================================
+ Coverage   75.82%   76.12%   +0.30%     
==========================================
  Files         519      528       +9     
  Lines       19235    19579     +344     
  Branches     3741     3829      +88     
==========================================
+ Hits        14584    14904     +320     
- Misses       3781     3792      +11     
- Partials      870      883      +13     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[cursor]

Stale Bugbot comment from a previous run.

Resolved

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

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 6bb5320. Configure here.}

[jamescrosswell]

@wedamija very close now - I think the cursor comment/finding is legit. I suggested we adopt the same approach we did for Hangfire.

Other than that, just one leftover comment from the old implementation to clean up and I think we're good to go.

[michaelmairegger]

@wedamija very close now - I think the cursor comment/finding is legit. I suggested we adopt the same approach we did for Hangfire.

Other than that, just one leftover comment from the old implementation to clean up and I think we're good to go.

Nice, that we are close to finish. And I am glad my contribution will find its path to final release

[jamescrosswell]

Looks good but currently blocked by this (nothing to do with you):

• ci: bump Microsoft.Playwright to 1.63.0 so Blazor WASM E2E tests run on Ubuntu 26.04 runners #5757

@wedamija @ric-oliv could I get one of you to approve the above?

[ric-oliv]

Sorry for adding comments so late here @wedamija and @jamescrosswell!
Please feel free to push this back to a future improvement issue if you prefer 🙏

[ric-oliv]

One last suggestion from my side 🙏

[jamescrosswell]

Huge thanks to @michaelmairegger @wedamija and @ric-oliv for getting this over the line!
❤️