Repository navigation
docs(crons): Add arq setup for Python - #20056
Conversation
Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
github-actions
Bot
added
the
Priority: Needs Triage
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.
This adds `monitor_cron_jobs` to `ArqIntegration`, matching Celery's
`monitor_beat_tasks`. When it's on, each `cron(...)` job sends check-ins
with its schedule in the worker's timezone, so Sentry creates the
monitor on the first run. The slug is the job name without arq's `cron:`
prefix. It's off by default.
```python
sentry_sdk.init(
integrations=[ArqIntegration(monitor_cron_jobs=True, exclude_cron_jobs=["cleanup"])],
)
```
Jobs check in without a config when Crons can't express the schedule: a
`second` other than 0, both `day` and `weekday` set, or a UTC offset
that isn't a whole number of hours. Before arq 0.25, the config is only
sent when the system timezone is UTC.
Docs: getsentry/sentry-docs#20056
Co-Authored-By: Claude <noreply@anthropic.com>
github-actions
Bot
added
Priority: Normal
|
The plan checks page loads for the changed Crons setup page, client errors on that page, and MDX-not-found logs. An issue escalates when those errors appear or page loads fall to zero. Monitoring in Services: Mention PlanWhat changedVisitors to RiskBad MDX can 404 the whole Python Crons page. Users then lose the Celery Beat link and Job Monitoring copy too. Intended effectThis change is a docs edit. Telemetry cannot show the new arq section. Regression watchThis page has low traffic. Sibling Celery Beat Crons loads were 3 in the same window. A drop of a few loads is noise. A fall to 0 while platform page loads stay near 8790 is a regression.
Not observableThe rendered HTML does not emit a signal for the arq heading. Get Slack DMs about this change: cursor.com/automations/rollouts |
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. This is a quick fix to keep the arq integration behaviour in line with how other integrations work. Sorry for the churn! Follow-up to #8051. Cron jobs whose schedule Crons can't express are no longer monitored, instead of checking in without a config. This matches Celery beat, and the Huey and RQ integrations from #8052 and #8053. Docs: getsentry/sentry-docs#20056 Co-authored-by: Claude <noreply@anthropic.com>
|
SDK release is coming out in a few mins, merging. |
## DESCRIBE YOUR PR Adds a Huey section to the Python Crons setup page: turning on `monitor_periodic_tasks`, how the slug is picked, and which periodic tasks are monitored. SDK PR: getsentry/sentry-python#8052 Stacked on #20056. Merge after the SDK release that includes it. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Ivana Kellyer <ivana.kellyer@sentry.io>
This branch was successfully deployed
2 participants
DESCRIBE YOUR PR
Adds an arq section to the Python Crons setup page: turning on
monitor_cron_jobs, how the slug is picked, and which cron jobs are monitored.SDK PR: getsentry/sentry-python#8051
Merge after the SDK release that includes it.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace
YYYY-MM-DDwith the due date. You can update this information later by editing the PR description.