Repository navigation
ref(server-utils): Share one cron converter across cron integrations - #25918
Merged
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
isaacs asked in review of #25013 for one cron converter, so
@SentryCron,Sentry.cron.*and the scheduler integrations read schedules the same way and can't drift apart. They now all use one converter in@sentry/server-utils, which takes the scheduler's dialect (node-cron,cronorcron-parser), since they read day fields, names and nicknames differently.For
Sentry.cron.instrumentCron,instrumentNodeCronandinstrumentNodeSchedule, this means: without a time zone, they send the server's time zone instead of letting Sentry assume UTC. Expressions Sentry would read differently than the scheduler, like per-second schedules or0 9 31 2,4 *, send no monitor config, so existing monitors keep their schedule.