Repository navigation
ref(crons): Add Fugit schedule conversion helper - #3141
Merged
Merged
Conversation
Add Sentry::Cron::FugitSchedule, which turns fugit cron lines and intervals into monitor configs. It returns nil for schedules Sentry would read differently. Shared by the rufus-scheduler and Solid Queue integrations. fugit is added as a dev dependency for the specs. Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Oct 16, 2026
Co-Authored-By: Claude <noreply@anthropic.com>
wedamija
marked this pull request as ready for review
October 16, 2026 22:57
Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Oct 17, 2026
sl0thentr0py
approved these changes
Oct 21, 2026
wedamija
added a commit
that referenced
this pull request
Oct 21, 2026
Part of a series that sends Crons monitor configs from Ruby schedulers. Check-ins for a monitor that does not exist yet are dropped, so today every monitor has to be created by hand with its schedule copied from the code. Sending the schedule lets Sentry create the monitor and keep it in sync. This adds an opt-in patch for rufus-scheduler: ```ruby config.enabled_patches << :rufus_scheduler ``` `cron` and `every` jobs send in-progress and ok/error check-ins, with the job's schedule as the monitor config. - The slug is the job's `name:`, or the handler's class or method. Unnamed blocks aren't monitored, and `sentry_monitor: false` opts a job out. - `interval` jobs and schedules Sentry can't represent check in without a config. One-off `in` and `at` jobs aren't monitored. - Errors still reach rufus's `on_error`. Stacked on #3141. The lockfile changes only add `rufus-scheduler` as a dev dependency. Docs: getsentry/sentry-docs#19789
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
2 participants
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 that sends Crons monitor configs from Ruby schedulers. Check-ins for a monitor that does not exist yet are dropped, so today every monitor has to be created by hand with its schedule copied from the code. Sending the schedule lets Sentry create the monitor and keep it in sync.
This adds
Sentry::Cron::FugitSchedule, which converts a Fugit cron or interval into a monitor config. Fugit is the schedule parser behind rufus-scheduler and Solid Queue, so both integrations use it: #3110 (rufus-scheduler) and #3140 (Solid Queue).It also converts Fugit syntax that has a Crons equivalent: the last day of the month (
L), the nth or last weekday of the month (mon#2,fri#-1), and whole-hour UTC offsets (+05:00becomesEtc/GMT-5).It returns nil when the schedule can't be expressed in the Crons schedule format, for example a job that runs every 10 seconds. Those jobs still send check-ins, but without a monitor config.
The SDK doesn't depend on Fugit. The lockfile changes only add it as a dev dependency for the specs.