Retries not effective for Upside Down 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

Hi, it looks like there might be a bug regarding upside-down push monitors and the retry functionality. As soon as the monitor receives the push signal, it switches from UP to DOWN immediately. Instead, I would expect it to go into ‘yellow state’, according to the retry settings, the same way that it does for an upside-down ping monitor.

👟 Reproduction steps

I have the following monitor setup:

• Push, Upside down
• Interval 600s
• Retries 144
• Retry Interval 600s
• Use case: monitor a server that’s supposed to be sleeping, and notify if it’s up for a long time (144*600s=1 day). Push type instead of ping, because the server wakes up on unicast!

As soon as the heartbeat is sent, the monitor switches to down state.

As a test, a similar ping monitor:

• Ping, Upside down
• Interval 30s
• Retries 4
• Retry Interval 30s
• Non-responding IP

The ping monitor is UP, because the fake IP does not respond. When I switch it to a valid IP, it goes down after 4 ‘yellow’ windows, and only then reports that it’s down.

👀 Expected behavior

Only go into down state when the push signal is received for retry_count consequtive windows, similar to the upside-down ping monitor

😓 Actual Behavior

Retry count does not seem to have any effect

🐻 Uptime-Kuma Version

1.17.1

💻 Operating System and Arch

Arch Linux

🌐 Browser

Firefox 101.0.1

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[ShadowGaming100]

But it does not work as intended, correct?

Correct

[ShadowGaming100]

Looks like http operates same as ping

I have tried http and there is no problem