starred/healthchecks

Fork 0

mirror of https://github.com/healthchecks/healthchecks.git synced 2026-04-25 06:55:53 +03:00

[GH-ISSUE #479] MQTT #357

New issue

Open

opened 2026-02-25 23:42:09 +03:00 by kerem · 7 comments

kerem commented

2026-02-25 23:42:09 +03:00

Owner

Originally created by @ronnyandre on GitHub (Feb 12, 2021).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/479

Firstly, thank you so much for a wonderful and POWERFUL software monitoring health for basically ANYTHING!

I thought it might be interesting to integrate to an MQTT broker. Should be fairly straight to add MQTT publish functionality to the app.

Thank you so much! 🙏

Originally created by @ronnyandre on GitHub (Feb 12, 2021). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/479 Firstly, thank you so much for a wonderful and POWERFUL software monitoring health for basically ANYTHING! I thought it might be interesting to integrate to an MQTT broker. Should be fairly straight to add MQTT publish functionality to the app. Thank you so much! 🙏

kerem added the

new integration

label

2026-02-25 23:42:09 +03:00

kerem commented

2026-02-25 23:42:10 +03:00

Author

Owner

@titanventura commented on GitHub (Jul 9, 2022):

Would like to work on this. Can you please guide me to do it ?

@titanventura commented on GitHub (Jul 9, 2022): Would like to work on this. Can you please guide me to do it ?

kerem commented

2026-02-25 23:42:10 +03:00

Author

Owner

@cuu508 commented on GitHub (Jul 11, 2022):

@ronnyandre @titanventura what use cases do you have in mind? Would Healthchecks be monitoring sensors (when e.g. incoming temperature readings stop, send an alert), or would it act as a sensor itself (when e.g. a cron job does not run on time, send a MQTT event to the broker)?

@cuu508 commented on GitHub (Jul 11, 2022): @ronnyandre @titanventura what use cases do you have in mind? Would Healthchecks be monitoring sensors (when e.g. incoming temperature readings stop, send an alert), or would it act as a sensor itself (when e.g. a cron job does not run on time, send a MQTT event to the broker)?

kerem commented

2026-02-25 23:42:10 +03:00

Author

Owner

@titanventura commented on GitHub (Jul 11, 2022):

Not sure. @ronnyandre , would you like to mention your use case ?

@titanventura commented on GitHub (Jul 11, 2022): Not sure. @ronnyandre , would you like to mention your use case ?

kerem commented

2026-02-25 23:42:10 +03:00

Author

Owner

@HardwareMan1000 commented on GitHub (Feb 29, 2024):

Hello there,
it would be nice to have a mqtt integration. My use case is that I run usb gsm dongle connected with sms2mqtt and standalone mqtt server. This allows me to send and receive sms messages from my internal systems using mqtt. I have integrated this with my home automation system and my homelab.

--update 03.03.2024
I did small python script for catching webhooks and pushing them to mqtt so it is not a very crucial feature.

Thanks in advance
BR

@HardwareMan1000 commented on GitHub (Feb 29, 2024): Hello there, it would be nice to have a mqtt integration. My use case is that I run usb gsm dongle connected with sms2mqtt and standalone mqtt server. This allows me to send and receive sms messages from my internal systems using mqtt. I have integrated this with my home automation system and my homelab. --update 03.03.2024 I did small python script for catching webhooks and pushing them to mqtt so it is not a very crucial feature. Thanks in advance BR

kerem commented

2026-02-25 23:42:10 +03:00

Author

Owner

@cuu508 commented on GitHub (Mar 5, 2024):

@HardwareMan1000 thanks. Do I understand it correctly, that:

you are running a MQTT broker
you would like Healthchecks to publish messages to the broker when a check goes up or down?

Would you be running a self-hosted Healthchecks instance in your local network?

Or would you be using the hosted service, and make your MQTT broker accessible from the public internet? In that case, how would authentication work?

If you are running a self-hosted instance, look into the Apprise integration, one of its many supported transports is MQTT: https://github.com/caronc/apprise/wiki/Notify_mqtt

@cuu508 commented on GitHub (Mar 5, 2024): @HardwareMan1000 thanks. Do I understand it correctly, that: * you are running a MQTT broker * you would like Healthchecks to publish messages to the broker when a check goes up or down? Would you be running a self-hosted Healthchecks instance in your local network? Or would you be using the hosted service, and make your MQTT broker accessible from the public internet? In that case, how would authentication work? If you are running a self-hosted instance, look into the [Apprise integration](https://healthchecks.io/docs/self_hosted_configuration/#APPRISE_ENABLED), one of its many supported transports is MQTT: https://github.com/caronc/apprise/wiki/Notify_mqtt

kerem commented

2026-02-25 23:42:10 +03:00

Author

Owner

@HardwareMan1000 commented on GitHub (Mar 5, 2024):

@cuu508 thanks for your attention.
Yes, thats correct.
At this moment I run mqtt broker in my local network as well as instance of healthchecks in a docker.

As you mentioned, there are few possible configurations but irregardless of its type (selfhosted or not) I think it's possible to just generate dedicated login-password for an HC app which you would just want to connect to mqtt broker. In my current setup I just wrote small python app which listens for http queries and using paho-mqtt just pushes formated data to mqtt broker.
My config is probably unusual and I don't expect broad support in doing strange setups but during setting HC instance in my local network I found this thread and your question to @ronnyandre so I add a little input to highlight possible usecase.

Thanks for pointing Apprise integration. Looks interesting and probably solves this problem.

@HardwareMan1000 commented on GitHub (Mar 5, 2024): @cuu508 thanks for your attention. Yes, thats correct. At this moment I run mqtt broker in my local network as well as instance of healthchecks in a docker. As you mentioned, there are few possible configurations but irregardless of its type (selfhosted or not) I think it's possible to just generate dedicated login-password for an HC app which you would just want to connect to mqtt broker. In my current setup I just wrote small python app which listens for http queries and using paho-mqtt just pushes formated data to mqtt broker. My config is probably unusual and I don't expect broad support in doing strange setups but during setting HC instance in my local network I found this thread and your question to @ronnyandre so I add a little input to highlight possible usecase. Thanks for pointing Apprise integration. Looks interesting and probably solves this problem.

kerem commented

2026-02-25 23:42:10 +03:00

Author

Owner

@danstreeter commented on GitHub (Apr 20, 2024):

I'd like to mirror the OP's first comment - thank you so much for a great tool. Been using it in my home lab for about 20 minutes and already changed my life!
I now know when otherwise unobservable crons are working (or not)!

I'd love MQTT integration, on potentially both the ingress and egress sides...

Ingress
Ability to listen to a topic, expecting a message at the defined scheduled basis (Like a cron)

(Real world) Use case: I know I should expect a message from my Hildebrand/Glow CAD every minute containing electric (and gas every 30 mins) data... if I do not - I need to know about it as without it my energy data is going to be skewed and it looks like I used a whole bunch of electric whenever the next message arrives rather than spread over the downtime period, it usually means either the device has gone down or offline, or the broker has gone offline.

This is rare - but the data feed is not something I was monitoring and had to create a nasty feeling node-red workflow to reset a timer every time a message comes in, and if the timer expires send another notification to get some level of monitoring at the moment. It usually happens when I am tinkering to be honest!

Egress
Send a message on a topic on the check state change.

@danstreeter commented on GitHub (Apr 20, 2024): I'd like to mirror the OP's first comment - thank you so much for a great tool. Been using it in my home lab for about 20 minutes and already changed my life! I now know when otherwise unobservable crons are working (or not)! I'd love MQTT integration, on potentially both the ingress and egress sides... **Ingress** Ability to listen to a topic, expecting a message at the defined scheduled basis (Like a cron) (Real world) Use case: I know I should expect a message from my [Hildebrand/Glow CAD](https://shop.glowmarkt.com/products/display-and-cad-combined-for-smart-meter-customers) every minute containing electric (and gas every 30 mins) data... if I do not - I need to know about it as without it my energy data is going to be skewed and it looks like I used a whole bunch of electric whenever the next message arrives rather than spread over the downtime period, it usually means either the device has gone down or offline, or the broker has gone offline. _This is rare - but the data feed is not something I was monitoring and had to create a nasty feeling node-red workflow to reset a timer every time a message comes in, and if the timer expires send another notification to get some level of monitoring at the moment. It usually happens when I am tinkering to be honest!_ **Egress** Send a message on a topic on the check state change.