docs(dotnet): Add Quartz.NET crons page

[wedamija]

DESCRIBE YOUR PR

Adds a .NET crons page for the new Quartz.NET packages: Sentry.Quartz for Quartz.NET 4.x (q.AddSentry()) and Sentry.Quartz3 for Quartz.NET 3.x (SentryJobListener). Jobs opt in with [SentryCronMonitorSlug], and the trigger's schedule is sent as the monitor config unless SendMonitorConfig is turned off. The crons index links to it next to Hangfire.

SDK PRs: getsentry/sentry-dotnet#5674, getsentry/sentry-dotnet#5668

Merge after the SDK release that includes them.

IS YOUR CHANGE URGENT?

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

[vercel]

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

Project	Deployment	Actions	Updated
sentry-docs	Ready	Preview	Oct 17, 2026 2:11am UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
develop-docs	Ignored	Preview	Oct 17, 2026 2:11am UTC

[jamescrosswell]

A few things on the Quartz page are out of date with the latest commits on getsentry/sentry-dotnet#5505:

1. Quartz.NET 4.x captures job exceptions again. Since getsentry/sentry-dotnet@73e5551, Sentry.Quartz captures what a job throws inside the job's scope, so the error is tagged with quartz.job and shares a trace with the check-in. This paragraph is now only true of Sentry.Quartz3, where the listener can't wrap the job. Maybe something like:

   With Quartz.NET 4.x, the SDK captures the exceptions jobs throw in the job's scope, so they're tagged with quartz.job and share a trace with the check-in. With Quartz.NET 3.x it doesn't: Quartz.NET logs them as errors, and Sentry's logging integration captures that log entry, for example when you use Sentry.AspNetCore or Sentry.Extensions.Logging.

   Line 39 could mention it too.

2. The attribute is now SentryMonitorSlug, renamed in the same commit to match Sentry.Hangfire. The old name is on lines 63, 66, 82, 90, 95, 111 and 125, including SentryCronMonitorSlugAttribute.JobDataKey in the data-map example.

3. Line 88 describes logging that's gone. Since getsentry/sentry-dotnet@fe97276, a job without an identity falls back to its class name with a debug message rather than a warning, and nothing checks for two jobs sharing a slug any more.