feat(nestjs): Add option to monitor every @Cron method - #25471

Part of a series adding automatic Crons monitoring for the most-used job schedulers in each SDK. Check-ins for a monitor that doesn't exist yet are dropped, so today each monitor has to be created by hand with its schedule copied from the code. Sending the job's schedule as the monitor config lets Sentry create the monitor and keep it in sync.

Description

Adds monitorCronJobs to nestIntegration. When enabled, every @Cron() method of @nestjs/schedule sends check-ins, with the schedule and time zone of @Cron() as the monitor config (same conversion as @SentryCron in #25013). It is off by default.

Sentry.init({
  dsn: '...',
  integrations: [
    Sentry.nestIntegration({
      monitorCronJobs: true,
      excludeCronJobs: ['cleanup', /^Dev/],
    }),
  ],
});

The slug is the name option of @Cron(), or ClassName.methodName without one. excludeCronJobs matches slugs (strings exactly, or regexes). Methods that also have @SentryCron keep their explicit slug and send one set of check-ins. Schedules Sentry would read differently (for example, a job that runs every 10 seconds) check in without a config. @Cron() with a Date runs once and is not monitored. This uses the @Cron instrumentation of the orchestrion channel injection, so it needs enableRuntimeChannelInjection (on by default).

Testing

Unit tests for slugs, exclusion, @SentryCron in both decorator orders, and error check-ins; an e2e test in nestjs-basic.

Stacked on #25013.