Add more details to Cron Check-In Issues
Open
Nobody has claimed this yet.
Crons
Improvement
Product Area: Crons
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Problem Statement
Cron check-in issues currently provide little to no detail about what caused the failure. The alert itself is fine, but the resulting Sentry issue is not actionable without a stack trace or error context.
Please include richer failure details, such as the stack trace.
Solution Brainstorm
No response
Product Area
Crons
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Cron check-in issue generation and failure-handling entry points, then inspect how the current alert details are passed into the Sentry issue. The work is done when failed check-ins include actionable error context, such as a stack trace, in the resulting issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100