Repository navigation
Conversation
Sends check-ins for every named job created with scheduleJob through the orchestrion channel injection. Cron strings (with their tz) are sent as the monitor config when Sentry reads them the same way; recurrence rules check in without a config. Unnamed and one-off jobs are skipped. Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Oct 17, 2026
Contributor
size-limit report 📦
|
Co-Authored-By: Claude <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
nodeScheduleIntegration, which sends check-ins for every named job created withscheduleJob(node-schedule1.3+ and 2.x), without wrapping the module inSentry.cron.instrumentNodeSchedule. Adding the integration is the opt-in.The slug is the job name. Jobs without a name get a generated name from
node-schedule, so they are not monitored; one-off jobs (aDate) aren't either. UnlikeinstrumentNodeSchedule, unsupported jobs are skipped instead of throwing.Cron strings are sent as the monitor config with their
tz(the server's time zone without one). Recurrence rules and object literals, schedules that can't be expressed in the Crons schedule format (for example, a job that runs every 10 seconds), and day-field combinations Sentry reads differently fromcron-parsercheck in without a config. Jobs already wrapped byinstrumentNodeScheduleare skipped.Testing
Node integration test with real
node-schedulein ESM and CJS; the conversion is unit tested in #25473.Stacked on #25473.