starred/healthchecks

Fork 0

mirror of https://github.com/healthchecks/healthchecks.git synced 2026-04-26 07:25:51 +03:00

[GH-ISSUE #167] Mastodon/Pleroma #115

New issue

Open

opened 2026-02-25 23:41:14 +03:00 by kerem · 8 comments

kerem commented

2026-02-25 23:41:14 +03:00

Owner

Originally created by @bortzmeyer on GitHub (Apr 30, 2018).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/167

I would like to have the possibility of a notification via Mastodon (or Pleroma, which has the same API). Here is an example on how to do it:

http://www.bortzmeyer.org/icinga-mastodon.html

Originally created by @bortzmeyer on GitHub (Apr 30, 2018). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/167 I would like to have the possibility of a notification via Mastodon (or Pleroma, which has the same API). Here is an example on how to do it: http://www.bortzmeyer.org/icinga-mastodon.html

kerem added the

new integration

label

2026-02-25 23:41:14 +03:00

kerem commented

2026-02-25 23:41:14 +03:00

Author

Owner

@cuu508 commented on GitHub (Dec 19, 2022):

@bortzmeyer, @bt90 would the notifications be private messages to a specific user?

@cuu508 commented on GitHub (Dec 19, 2022): @bortzmeyer, @bt90 would the notifications be private messages to a specific user?

kerem commented

2026-02-25 23:41:14 +03:00

Author

Owner

@bt90 commented on GitHub (Dec 19, 2022):

Apprise supports both. Public toots and DMs are both valid usecases IMHO.

@bt90 commented on GitHub (Dec 19, 2022): Apprise supports [both](https://github.com/caronc/apprise/wiki/Notify_mastodon#example). Public toots and DMs are both valid usecases IMHO.

kerem commented

2026-02-25 23:41:14 +03:00

Author

Owner

@bt90 commented on GitHub (Dec 19, 2022):

Apprise supports both. Public toots and DMs are both valid usecases IMHO.

@bt90 commented on GitHub (Dec 19, 2022): Apprise supports [both](https://github.com/caronc/apprise/wiki/Notify_mastodon#example). Public toots and DMs are both valid usecases IMHO.

kerem commented

2026-02-25 23:41:14 +03:00

Author

Owner

@cuu508 commented on GitHub (Dec 19, 2022):

@bt90 Healthchecks already has Apprise integration, which you can enable and use on a self-hosted instance.

I'm thinking whether or not it would be useful to have a more locked-down integration on https://healthchecks.io:

One bot user configured per instance (i.e., the user cannot specify what user account to post from)
A fixed notification template (i.e., the user cannot enter a free-form message to be posted on state changes)
Private messages only, as I don't think it makes sense for the bot to post public notifications for all users in one noisy stream

A similar existing integration is Telegram – there's a single bot user configured per Healthchecks instance, and it posts templated notifications to a designated user/group.

@cuu508 commented on GitHub (Dec 19, 2022): @bt90 Healthchecks already has Apprise integration, which [you can enable](https://healthchecks.io/docs/self_hosted_configuration/#APPRISE_ENABLED) and use on a self-hosted instance. I'm thinking whether or not it would be useful to have a more locked-down integration on https://healthchecks.io: * One bot user configured per instance (i.e., the user cannot specify what user account to post *from*) * A fixed notification template (i.e., the user cannot enter a free-form message to be posted on state changes) * Private messages only, as I don't think it makes sense for the bot to post public notifications for all users in one noisy stream A similar existing integration is Telegram – there's a single bot user configured per Healthchecks instance, and it posts templated notifications to a designated user/group.

kerem commented

2026-02-25 23:41:14 +03:00

Author

Owner

@bt90 commented on GitHub (Dec 19, 2022):

With a single user it would only make sense to use DMs. If the Mastodon account would be configurable, it would also allow users to run a monitoring account which can be followed.

e.g. "follow @myservice@botsin.space to get notified on downtimes!"

@bt90 commented on GitHub (Dec 19, 2022): With a single user it would only make sense to use DMs. *If* the Mastodon account would be configurable, it would also allow users to run a monitoring account which can be followed. e.g. "follow @myservice@botsin.space to get notified on downtimes!"

kerem commented

2026-02-25 23:41:14 +03:00

Author

Owner

@thibaultmol commented on GitHub (Feb 23, 2024):

Now that Mastodon/fediverse is getting more popular, might be interesting to revisit this!

@thibaultmol commented on GitHub (Feb 23, 2024): Now that Mastodon/fediverse is getting more popular, might be interesting to revisit this!

kerem commented

2026-02-25 23:41:14 +03:00

Author

Owner

@cuu508 commented on GitHub (Feb 23, 2024):

Perhaps, but I need to understand the use case, and get some idea how this would work technically.

Regarding the use case:

When and why would you want to be notified through Mastodon?
Would you want (semi-)private downtime notifications delivered to you?
Or would you want a bot account that posts public downtime notifications, that anyone can follow? Like public status pages, but using Mastodon as the medium?

If you want private notifications, why through Mastodon? Federation can have delays, push notification delivery to the client apps can have delays (or not work at all as is currently the case with the Mastodon client I'm using). I view Mastodon as a news stream that's delivered to me on best effort basis. If some messages get lost, or I don't notice them in my timeline, no big deal. I personally would not want to rely on it for anything mission critical.

For the bot account case, would the user provide bot account's credentials to Healthchecks, so Healthchecks can post on their behalf? Would it in the end boil down to Healthchecks firing off one or two HTTP requests to the Mastodon instance that the user has configured?

@cuu508 commented on GitHub (Feb 23, 2024): Perhaps, but I need to understand the use case, and get some idea how this would work technically. Regarding the use case: * When and why would you want to be notified through Mastodon? * Would you want (semi-)private downtime notifications delivered to you? * Or would you want a bot account that posts public downtime notifications, that anyone can follow? Like public status pages, but using Mastodon as the medium? If you want private notifications, why through Mastodon? Federation can have delays, push notification delivery to the client apps can have delays (or not work at all as is currently the case with the Mastodon client I'm using). I view Mastodon as a news stream that's delivered to me on best effort basis. If some messages get lost, or I don't notice them in my timeline, no big deal. I personally would not want to rely on it for anything mission critical. For the bot account case, would the user provide bot account's credentials to Healthchecks, so Healthchecks can post on their behalf? Would it in the end boil down to Healthchecks firing off one or two HTTP requests to the Mastodon instance that the user has configured?

kerem commented

2026-02-25 23:41:14 +03:00

Author

Owner

@thibaultmol commented on GitHub (Feb 23, 2024):

When and why would you want to be notified through Mastodon?

More as a way of giving people flexibility to subscribe wherever they want

Would you want (semi-)private downtime notifications delivered to you?

I suppose not? Just a way of informing the public that use your services when there is an outage.

Or would you want a bot account that posts public downtime notifications, that anyone can follow? Like public status pages, but using Mastodon as the medium?

Yes, exactly.
I already follow the Belgian E-health status (unoficial) monitor through Mastodon and it's pretty instant if you have notifications turned on tbh

I personally would not want to rely on it for anything mission critical.

This isn't the 'for me' notifications, this is the public notifications.
Like the Belgian E-Health monitor. It's unofficial in this case, it just helps to see if we (pharmacy) experience downtime, that we can confirm through that monitor that there is indeed downtime.
Internally they have their own official monitoring setup, this is just something created by a 3rd party.
(to be clear, they don't use healthchecks, i'm using it as an example of why a public "is it down?" style mastodon account for a service might be useful)

@thibaultmol commented on GitHub (Feb 23, 2024): > When and why would you want to be notified through Mastodon? More as a way of giving people flexibility to subscribe wherever they want > Would you want (semi-)private downtime notifications delivered to you? I suppose not? Just a way of informing the public that use your services when there is an outage. > Or would you want a bot account that posts public downtime notifications, that anyone can follow? Like public status pages, but using Mastodon as the medium? Yes, exactly. I already follow the Belgian E-health status (unoficial) monitor through Mastodon and it's pretty instant if you have notifications turned on tbh > I personally would not want to rely on it for anything mission critical. This isn't the 'for me' notifications, this is the public notifications. Like the Belgian E-Health monitor. It's unofficial in this case, it just helps to see if we (pharmacy) experience downtime, that we can confirm through that monitor that there is indeed downtime. Internally they have their own official monitoring setup, this is just something created by a 3rd party. (to be clear, they don't use healthchecks, i'm using it as an example of why a public "is it down?" style mastodon account for a service might be useful)