Uptime after clear data heartbeats is wrong #1936

Closed
opened 2026-02-28 02:37:37 -05:00 by deekerman · 0 comments
Owner

Originally created by @Opwi on GitHub (Feb 24, 2023).

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

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

I use push monitor.
This is the behavior that I have: https://youtu.be/MbNdrboQLJs

The only option to solve this issue after the behavior in this video is to restart the docker compose. After this, the value of the uptime is to 100%, which is the good value.

I'm not sure this comportment is the same on other types of monitors.

👟 Reproduction steps

  • host is up
  • host is down
  • host is up after the down
  • clear data heartbeats
  • look at the uptime

👀 Expected behavior

After the clear data heartbeats button, the uptime must be reset and not keeping the older value.

😓 Actual Behavior

After the clear data heartbeats button, the uptime keep the older value before the clear data heartbeats.

🐻 Uptime-Kuma Version

1.20.1

💻 Operating System and Arch

Debian 11

🌐 Browser

Google Chrome 110.0.5481.177

🐋 Docker Version

Docker version 23.0.1

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Originally created by @Opwi on GitHub (Feb 24, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description I use push monitor. This is the behavior that I have: https://youtu.be/MbNdrboQLJs The only option to solve this issue after the behavior in this video is to restart the docker compose. After this, the value of the uptime is to 100%, which is the good value. I'm not sure this comportment is the same on other types of monitors. ### 👟 Reproduction steps - host is up - host is down - host is up after the down - clear data heartbeats - look at the uptime ### 👀 Expected behavior After the clear data heartbeats button, the uptime must be reset and not keeping the older value. ### 😓 Actual Behavior After the clear data heartbeats button, the uptime keep the older value before the clear data heartbeats. ### 🐻 Uptime-Kuma Version 1.20.1 ### 💻 Operating System and Arch Debian 11 ### 🌐 Browser Google Chrome 110.0.5481.177 ### 🐋 Docker Version Docker version 23.0.1 ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output _No response_
deekerman 2026-02-28 02:37:37 -05:00
  • closed this issue
  • added the
    bug
    label
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#1936
No description provided.