Integrate Sentry error reporting into the Hackbot broker
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
The broker (job container, which holds tokens and brokers Phabricator/Bugzilla/etc. access on behalf of the credential-less agent container) has no Sentry integration today, so broker-side exceptions (auth failures, action-apply errors, webhook processing) are not captured anywhere. Add the Sentry SDK to hackbot-api so these errors are visible and can be triaged.
Relevant code: services/hackbot-api/app/jobs.py:42-44, libs/hackbot-runtime/hackbot_runtime/revision.py:33-46.
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 reading services/hackbot-api/app/jobs.py:42-44 and libs/hackbot-runtime/hackbot_runtime/revision.py:33-46 to understand the broker's job and revision error paths. Add Sentry SDK integration to hackbot-api so broker-side auth failures, action-apply errors, and webhook processing exceptions are captured and available for triage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, observability-sre
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100