opensearch-project / opensearch-project/alerting
Support alerts to be sent to RabbitMQ as a destination
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 82
- Forks
- 133
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 9
Description
Sunday Sep 06, 2020 at 07:14 GMT
Originally opened as https://github.com/opendistro-for-elasticsearch/alerting/issues/250
Is your feature request related to a problem? Please describe.
RabbitMQ use queue protocol AMQP that is by design different from webhook so the only way is to open a github issue
Describe the solution you'd like
Support RabbitMQ as a destination
Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.
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
No files, tests, or entry points are named. Start by reviewing the alerting repository's current destination support and RabbitMQ's AMQP requirements, then identify the integration boundary and test coverage needed. Done means RabbitMQ is supported as an alert destination and the behavior is verified by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, rabbitmq
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100