No down notifications for push monitor

⚠️ Please verify that this bug has NOT been raised before.

• I checked and didn’t find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

I have a push monitor configured for a 1min interval. It appears that since upgrading, it no longer sends notification for missed heartbeats:

You’ll notice that between 8:14 and 8:21 there were no pings, but no down notifications were sent either.

I wonder if it has something to do with the failed SMTP notifications shown in the logs below, but I have the same issue on all my monitors and those send the gotify notifications just fine

👟 Reproduction steps

Configure a push monitor as below:

Ping the URL every minute for a while Stop pinging the URL

👀 Expected behavior

Get a down notification

😓 Actual Behavior

Only get up notifications

🐻 Uptime-Kuma Version

1.10.2

💻 Operating System and Arch

Docker on Ubuntu 20.04

🌐 Browser

Firefox

🐋 Docker Version

20.10.10, build b485636

🟩 NodeJS Version

No response

📝 Relevant log output

onitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP

[louislam]

Finally addressed the issue, it should be fixed in the next release

[hansenc0705]

I seem to be having this issue as well. I setup a new PUSH monitor and before i triggered my first GET to the URL i did get a down alert, triggered my GET to the URL and got an up alert then I didn’t trigger another GET to the URL and haven’t received an alert but can see in the WebUI that its down but the history doesn’t call it out. If I do a GET to the URL I will get an Up alert.

Steps to duplicate Create new PUSH monitor using settings below Don’t do anything and get your first down alert Then load the URL, i’m doing a powershell web request with the method GET you will get an UP alert Wait configured time to miss a heartbeat, you will see the WebUI show it as down but no alerts Then trigger a GET to the URL