You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Aaron Fischer 6c9e57c226 Merge pull request 'dockerize' (#1) from dockerize into master 2 weeks ago
.build.yml Add minimal CI build 7 months ago
.gitignore Refactor, read configuration from file 2 years ago
Dockerfile Add minimal Dockerfile and docker-compose 2 weeks ago
LICENSE Add LICENSE (GPLv3) 2 years ago Add CI badge, contact. 7 months ago
config.toml.sample Allow HTTP listen address configuration 2 years ago
docker-compose.yml Add minimal Dockerfile and docker-compose 2 weeks ago
go.mod Fix the go.mod and add the go.sum 2 weeks ago
go.sum Fix the go.mod and add the go.sum 2 weeks ago
main.go Display name label on matrix notification 2 years ago Properly handle incoming hooks 2 years ago

matrix-alertmanager-receiver status

Simple daemon - less than 150 lines of Go - forwarding prometheus-alertmanager events to matrix room. While there already is a matrix-alertmanager project out there, use of the JavaScript ecosystem made it rather painful to use from my point of view.

Feel free to directly send me patches and questions by email.


Make sure you have Go installed (golang-bin package on Fedora).

go build -v


Note: you are supposed to expose this service via a proxy such as Nginx, providing basic HTTP authentication.

I (master|✚1) ~/W/f/matrix-alertmanager-receiver » ./matrix-alertmanager-receiver --help
Usage of ./matrix-alertmanager-receiver:
  -config string
    	Path to configuration file (default "/etc/matrix-alertmanager-receiver.toml")
I [2] (master|✚1) ~/W/f/matrix-alertmanager-receiver » cat config.toml
Homeserver = ""
TargetRoomID = "!"
MXID = ""
MXToken = "secretsecretsecret"
HTTPPort = 9088
HTTPAddress = ""
I (master|✚1) ~/W/f/matrix-alertmanager-receiver » ./matrix-alertmanager-receiver -config config.toml
2020/05/03 10:50:47 Reading configuration from config.toml.
2020/05/03 10:50:47 Connecting to Matrix Homserver as
2020/05/03 10:50:47 is already part of !
2020/05/03 10:50:47 Listening for HTTP requests (webhooks) on :9088
2020/05/03 10:50:55 Received valid hook from [::1]:44886
2020/05/03 10:50:55 > FIRING instance example1 is down