vectordotdev / vectordotdev/vector
New `prometheus_alertmanager` source and sink
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
Hi, I have just started using prometheus (using statsd_source and prometheus_sink). Is there any plans to implement an alertmanager sink and source?
Although the alertmanager primarily consumes alerts from prometheus, it does have a REST API to inject alerts from external systems which are combined with tags to create de-duped alerts.
It appears to be able to send out alerts to a generic HTTP end-point, which could be a vector component to act as a source for alerts.
Hopefully this will allow vector to provide the glue logic to join user apps into the alerting framework.
Thoughts, from other people?
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 reviewing the existing statsd_source and prometheus_sink components, then examine the Alertmanager REST API described in the issue. Define the source and sink behavior, including how external alerts and generic HTTP alerts should be represented, before determining what tests are needed to show the feature is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus, rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100