Alerting

[heartbeat-sh]

Alerting

[arieroos]

There is currently no alerting, but it is definitely something to consider.

Before we build alerting, we will need to build a way to authorize heartbeats, and only authorized heartbeats will generate alerts. Otherwise we will be opening doors to spam.

[bartoruiz]

This is what I did. I ran a cron every 1min in my linux server and get emails alerts:

#!/bin/sh
emailto="[email protected]"
subject="HEARTBEAT"

json=$(
  curl -X GET 'https://yourdomain.heartbeat.sh/heartbeats' \
  --compressed \
  -s
)

errors=`echo -n $json | grep -o '"Status":"ERROR"' | wc -l | awk '{print $1}'`;
echo ERRORS: $errors

if [ $errors != 0 ]; then
        msgsubj="$subject ERRORS: $errors"
        echo $json | mail -s "${msgsubj}" ${emailto}
fi

[rudolfbyker]

@arieroos if you implement alerts, I think alerting only on the "falling edge" of the signal (i.e. transition from green to orange/red) is much more useful than alerting repeatedly alerting like the above example. In my experience, if I can't address an issue immediately, the flood of e-mails makes me counter-productive.

A client-side-only way of doing this would be to make the web interface into a PWA, which makes it installable, and provides a service worker. Then the service worker kan show notifications. https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorkerRegistration/showNotification Depending on the device, the notifications might not work when the app is put to sleep (e.g. most Androids) but it still has some use, and does not require you to push anything from a server, keeping the implementation simple.