prometheus / prometheus/alertmanager

Eventstream endpoint

Open
#1,304 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

kind/enhancement stale
Dominant language
Go
Stars
8.6k
Forks
2.5k
Avg merge
2d 6h
Merged PRs (30d)
61

Description

Live update endpoint, like a websocket that you can subscribe to that receives updates based on mesh info, incoming alerts, when an alert is silenced. Clients could consume this to e.g. live update the AM UI, or update a Prometheus UI to show an alert is silenced or the last time a notification was sent

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.

Research direction

Start by mapping Alertmanager's existing API and the paths that process mesh information, incoming alerts, silences, and notification events. Define the eventstream's subscription and event semantics, then determine how clients such as the AM UI or Prometheus UI would consume it; the issue does not name files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.