openbullet / openbullet/OpenBullet2

[REQUEST]: Add ability to monitor other things

Open
#1,166 1 comment 0 reactions 1 assignee View on GitHub

@openbullet is already working on this.

Since Mar 1, 2025.

enhancement question
Dominant language
C#
Stars
2.4k
Forks
602
PR merge metrics
No merged PRs in 30d

Description

This feature request respects the following points:
  • This is a feature request, not a question or a configuration issue; Please visit our forum first to troubleshoot with volunteers, before creating a report. The links can be found here.
  • This issue is not already reported on GitHub (I've searched it).
  • I'm using an up to date version of OpenBullet2. We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
  • I agree to follow OpenBullet's Code of Conduct.
  • This report addresses only a single feature request; If you have multiple feature request, kindly create separate reports for each one.
Description of the feature request

Adding a "custom webhook" feature to Monitor feature. It would help in real-time listening for my OB2 Web API project.

Is your feature request related to a problem

I'm always frustrated when the things don't go in "event-based" architecture. It would be shame if I were to setup a timer that sent a http request to OB2 endpoint every 5 seconds just to check real-time status of jobs.

Describe the solution you'd like

Adding custom webhook for the Monitor feature.

Describe alternatives you've considered

Seting up a timer that checks the jobs every 5 seconds. Very lame, not event-based, not really-time.

Relevant screenshots or videos

No response

Additional information

It would be useful if the Monitor also worked for other changes in the instance. Like adding and removing proxies, wordlists and such.

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.