No description
Find a file
2024-11-07 13:54:21 +01:00
cache cache/redis: Rig up timeout with context 2023-07-14 15:10:40 +02:00
config config: Allow to separate the ntfy topic from the server 2024-11-07 13:54:21 +01:00
contrib Add testing setup 2024-11-06 13:03:29 +01:00
docker docker: Recommend valkey 2024-11-06 15:06:29 +01:00
.build.yml Try out just 2024-11-03 19:38:20 +01:00
.gitignore version: Use linker flag 2023-02-16 13:06:21 +01:00
.justfile Add testing setup 2024-11-06 13:03:29 +01:00
config.scfg config: Allow to separate the ntfy topic from the server 2024-11-07 13:54:21 +01:00
functions.go functions: Use slices package for sorting 2023-08-11 13:50:53 +02:00
go.mod Upgrade go-utils 2023-08-13 16:06:09 +02:00
go.sum Upgrade go-utils 2023-08-13 16:06:09 +02:00
http.go Set default header for User-Agent 2023-02-20 13:27:41 +01:00
LICENSE Initial commit 2022-10-09 14:19:48 +02:00
main.go config: Allow to separate the ntfy topic from the server 2024-11-07 13:54:21 +01:00
README.md Let a label specify its own ntfy topic 2024-11-06 14:16:36 +01:00
silence.go Remove unnecessary Body.close() calls 2023-09-22 22:35:16 +02:00

ntfy-alertmanager

builds.sr.ht status

A bridge between ntfy and Alertmanager.

Installation

Simply use go build or the docker image with docker compose file. ntfy-alertmanager:latest is built from the latest tagged release while ntfy-alertmanager:dev is built from the master branch. On Arch Linux you can install the aur package as well.

Configuration

You can specify the configuration file location with the --config flag. By default the configuration file will be read from /etc/ntfy-alertmanager/config. The format of this file is scfg and there is an example configuration file in this repo. Furthermore you can take a look at my deployment.

ntfy-alertmanager has support for setting ntfy priority, tags, icon, action buttons (which can be used to e.g. create an Alertmanager silence or open the alert's Prometheus URL), email notifications and phone calls. Define a decreasing order of labels in the config file and map those labels to tags, priority, an icon, an email address or an alternative ntfy topic.

  • For priority and icon the first found value will be chosen. Settings for "resolved" alerts will take precedence.
  • Tags are added together.

Alertmanager config

receivers:
  - name: "ntfy"
    webhook_configs:
      - url: "http://127.0.0.1:8080"
        http_config:
          basic_auth:
            username: "webhookUser"
            password: "webhookPass"

Contributing

Report bugs on the issue tracker, send patches/ask questions on the mailing list or write to me directly on matrix @xenrox:xenrox.net. There is a mirror on Codeberg as well, where you can create issues or open pull requests.