No description
  • Rust 96.8%
  • Go Template 2.6%
  • Shell 0.6%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Jonas Eriksson af6f2ea0ab
All checks were successful
build / build (push) Successful in 42m16s
build / check (push) Successful in 8m3s
Update URL
2026-10-02 22:26:47 +02:00
.forgejo/workflows Dependency and Rust update 2026-10-01 20:41:07 +02:00
build-helpers Switch to Forgejo builds 2026-09-23 16:23:51 +02:00
src Silence key backup message 2026-10-02 22:18:21 +02:00
.gitignore First public version 2023-03-03 08:59:10 +01:00
.pre-commit-config.yaml Add pre-commit config 2024-02-12 21:49:48 +01:00
Cargo.lock Bump version 2026-10-02 22:19:26 +02:00
Cargo.toml Update URL 2026-10-02 22:26:47 +02:00
Containerfile.alpine Dependency and Rust update 2026-10-01 20:41:07 +02:00
COPYING Add actual license file too 2023-03-03 17:56:27 +01:00
README.md Update URL 2026-10-02 22:26:47 +02:00

mawby -- Matrix Alertmanager Webhook Bot? Yes!

Running

The easiest way right now is to use the container packaging. Builds are automatically uploaded to quay.io/upto/mawby. Three label types are available:

  • latest: Latest stable version
  • master: Latest version from the master branch
  • <version, such as v0.1.0>: Static version

Inside the container, mawby is running as an unprivileged user (mawby, uid/gid 9823/9823). By default, the configuration is read from /etc/mawby/mawby.conf, and it requires a writeable data directory at /var/lib/mawby (possible to change in the configuration). The default listening port is 9823, unless overriden by configuration.

To print a commented configuration template, run the application (or the container) with the argument --print-config-template.

Using

mawby expects WebhookV4 alerts to be posted to /alerts/<endpoint name>. Using the routing statements, this alert will be routed to the expected room. For example, with this alertmanager.yml fragment:

receivers:
  - name: service_a
    webhook_configs:
      - url: http://<mawby-host>:9823/alerts/service_a

And this mawby.yaml fragment:

rooms:
  team1: '#team1:example.org'

routes:
  service_a:
    room: team1

Alerts that are routed to the service_a receiver in alertmanager will end up in #team1:example.org. Since routing on labels and annotations is fully supported by alertmanager, mawby takes a more simplistic approach to routing and only supports routing between endpoints and rooms.

See https://forge.upto.se/mawby/mawby/src/branch/master/src/files/mawby.sample.yaml for a complete mawby configuration.