4 ms·
The issue with an alarm only when something is wrong, is that you don't know that your monitoring system is working until you actually get that notification. Yo
by sathackr 5y ago
The issue with an alarm only when something is wrong, is that you don't know that your monitoring system is working until you actually get that notification. You could just check the system every day and avoid the 'heartbeat' email, but that's likely to be forgotten/missed more often than seeing/reading the received email.
You could set up a monitoring system for the monitoring system...
- Chris2048 5y ago> You could set up a monitoring system for the monitoring system... I'm considering this for a home automation system: a smaller, simpler device connected to the network, powered via battery (recharged from mains but surge protected) aka UPS, and able to send SMS messages via mobile network. The idea is it's a heartbeat/monitoring system for the essentials: - power cut/outage - network down/outage - main server down, or has some problem Then I can get an SMS telling me something's wrong.
- lostlogin 5y agoPingdom integration or similar may be an option. There are some very cheap or free options out there. Checking from outside is not ideal though as a network outage looks the same as a sinking, a leak or any other problem.
- batch12 5y agoI do this in Splunk for some events. I alert for no events received within X period of time.
- IgorPartola 5y agoHASS has the ability to send you alerts when a device/sensor is considered to be offline (so you could definite it as it’s offline if it hasn’t sent you an update in 28 hours or some such). You can also set it up to send you regular notifications too. Or you could just have this data in the dashboard and check it once in a while. Nothing really prevents you from doing all this but also utilizing a tool like that to WUPHF.com you soon as there is an issue.