feature: Add Discord webhooks to Alerters #820

New Issue

2026-03-22T16:53:20-05:00

GiteaMirror commented

2026-03-22 16:53:20 -05:00

Originally created by @LawMixer on GitHub (Aug 9, 2024).

I do not use Slack unfortunately, but I do use Discord daily - would love to make this a thing!

Originally created by @LawMixer on GitHub (Aug 9, 2024). I do not use Slack unfortunately, but I do use Discord daily - would love to make this a thing!

GiteaMirror added the done label 2026-03-22 16:53:20 -05:00

GiteaMirror closed this issue

2026-03-22 16:53:22 -05:00

GiteaMirror commented

2026-03-22 16:53:24 -05:00

@mbecker20 commented on GitHub (Aug 9, 2024):

Agreed, slack is good for businesses but not individuals, I have this in my todo. There is also structure to add this and many more inbuilt endpoints.

Additionally, if you know Rust, you can use the starter codebase I made for building Custom Alerters. https://github.com/mbecker20/monitor/tree/main/bin/alerter.
Once you have the Alert in code you can do whatever you want with it.

@mbecker20 commented on GitHub (Aug 9, 2024): Agreed, slack is good for businesses but not individuals, I have this in my todo. There is also structure to add this and many more inbuilt endpoints. Additionally, if you know Rust, you can use the starter codebase I made for building Custom Alerters. [https://github.com/mbecker20/monitor/tree/main/bin/alerter](https://github.com/mbecker20/monitor/tree/main/bin/alerter). Once you have the Alert in code you can do whatever you want with it.

GiteaMirror commented

2026-03-22 16:53:25 -05:00

@mbecker20 commented on GitHub (Aug 9, 2024):

You can also use Vector (https://vector.dev/) as Custom Alerter endpoint

See https://vector.dev/docs/reference/configuration/sources/http_server/

Then you can route alerts to any of the Vector Sinks here: https://vector.dev/docs/reference/configuration/sinks/

You can consider a logging stack like Grafana / Loki / Tempo, or VictoriaLogs stack, to send all logs / alerts to. Then route what you want to your messaging like Discord from there. This is more scalable setup and kind of fun to set up if you are into this. You can set up all the containers with Monitor too

@mbecker20 commented on GitHub (Aug 9, 2024): You can also use Vector ([https://vector.dev/](https://vector.dev/)) as Custom Alerter endpoint See [https://vector.dev/docs/reference/configuration/sources/http_server/](https://vector.dev/docs/reference/configuration/sources/http_server/) Then you can route alerts to any of the Vector Sinks here: [https://vector.dev/docs/reference/configuration/sinks/](https://vector.dev/docs/reference/configuration/sinks/) You can consider a logging stack like Grafana / Loki / Tempo, or VictoriaLogs stack, to send all logs / alerts to. Then route what you want to your messaging like Discord from there. This is more scalable setup and kind of fun to set up if you are into this. You can set up all the containers with Monitor too

GiteaMirror commented

2026-03-22 16:53:26 -05:00

@TomKauffeld commented on GitHub (Sep 8, 2024):

While Discord is not implemented, you can already send notifications to a Channel using Discord Slack-Compatible Webhook:

Create a webhook in Discord on the channel you want the message
Create a new Alerter on Komodo with as Endpoint type Slack
Paste the webhook url as the endpoint with /slack at the end

@TomKauffeld commented on GitHub (Sep 8, 2024): While Discord is not implemented, you can already send notifications to a Channel using [Discord Slack-Compatible Webhook](https://discord.com/developers/docs/resources/webhook#execute-slackcompatible-webhook): - Create a webhook in Discord on the channel you want the message - Create a new Alerter on Komodo with as Endpoint type Slack - Paste the webhook url as the endpoint with `/slack` at the end