Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Integrate Sentry error reporting into the Hackbot broker

Open
  • Is something wrong?
#6,618 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend, observability-sre

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.

Description

hackbot

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.

Dominant language
Python
Stars
571
Forks
355
Avg merge
2d 2h
Merged PRs (30d)
78

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/bugbug

All issues in mozilla/bugbug

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.