Zetema
Edit
Infra & DevOps · A few weeksAnywhere· Source · May 2026

Teams that chat on Matrix can't get Alertmanager alerts there without running a separate bridge.

Teams that use the Matrix chat protocol and Prometheus Alertmanager

Where it stands

  1. Sourced (done)
  2. Kit (done)
  3. Wanted (next)
  4. Building
  5. Solved

How this problem came to be

  1. Found2 sourcesgithub.com/prometheus
  2. Quoted3 claimseach checked against its page
  3. BriefWrittenand what solved looks like
  4. Market1 signals21 reactions on the issue
  5. Kit5 steps20 tools · 6 routes
  6. People0 want0 live it · 0 would test

The problem, broken down

Who it hurts
Operations teams, open-source projects and public bodies that use Matrix, an open chat protocol, for team chat.
The moment
When an alert fires and the team's chat room stays silent.
What people do today
People run one of several third-party bridges, or switch to Grafana alerting with a webhook forwarder.
Why it's unsolved
It is unclear whether a built-in receiver needs end-to-end encryption, which is much harder than posting a plain message.
What solved looks like
A Matrix receiver in Alertmanager configured with homeserver address, room id and an access token read from a file, posting firing and resolved alerts with the standard templates, with an integration test against a local Matrix server in Docker.

Evidence

Every claim is tied to the source it comes from
Alertmanager issue #3919: Matrix receiver ↗
  1. 1The request for a built-in Matrix receiver was opened in July 2024 and is labelled ‘help wanted’.
  2. 2Commenters list several separate bridge projects people run instead, and one still hoped it would happen upstream.
  3. 3One commenter suggested a first version could post messages through the REST API without end-to-end encryption; another said they moved to Grafana alerting with a forwarder.

Written from the cited sources. Anything they don't say is left as a question, not a guess.

Sources

From a public page with a citation.

  1. [1]Alertmanager issue #3919: Matrix receiver
  2. [2]Matrix client-server API
What the source says, in short

The request for a built-in Matrix receiver was opened in July 2024 and is labelled ‘help wanted’. Commenters list several separate bridge projects people run instead, and one still hoped it would happen upstream. One commenter suggested a first version could post messages through the REST API without end-to-end encryption; another said they moved to Grafana alerting with a forwarder.

Forks 0

Nobody has forked this yet. Be the first.

Market read

How big this is, from the evidence

  • GitHub ↗Builders' pull · Medium confidence21 reactions on the issue

How these were measured: Total reactions on the GitHub issue, read from its API.

For whoever takes this up

The builder's path for this problem

Five steps, each with the tools that fit this problem and a word to carry with you. A starter prompt is ready to paste into any assistant.

Open the path

Discussion 0

No comments yet.