louislam / uptime-kuma

A fancy self-hosted monitoring tool
https://uptime.kuma.pet
MIT License
56.58k stars 5.08k forks source link

Adding a new child monitor results in a period of unavailable due to alignment #3920

Open nneul opened 11 months ago

nneul commented 11 months ago

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

🛡️ Security Policy

Description

image

👟 Reproduction steps

Define a monitor group, later add a new monitor to it.

👀 Expected behavior

Period when monitor did not exist should be treated as available or neutral, not unavailable.

😓 Actual Behavior

Resulted in a period of orange on the charge.

🐻 Uptime-Kuma Version

1.23.3

💻 Operating System and Arch

Ubuntu 20.04 x86

🌐 Browser

Chrome

🐋 Docker Version

24.0.6

🟩 NodeJS Version

No response

📝 Relevant log output

2023-10-19T15:50:08-05:00 [MONITOR] INFO: Added Monitor: undefined User ID: 1
2023-10-19T15:50:45-05:00 [MONITOR] INFO: Added Monitor: undefined User ID: 1
2023-10-19T15:50:45-05:00 [MANAGE] INFO: Resume Monitor: 4 User ID: 1
2023-10-19T15:50:45-05:00 [MONITOR] INFO: Added Monitor: undefined User ID: 1
2023-10-19T15:50:47-05:00 [MANAGE] INFO: Resume Monitor: 3 User ID: 1
2023-10-19T15:50:53-05:00 [MONITOR] INFO: Get Monitor: 3 User ID: 1
2023-10-19T15:51:01-05:00 [MANAGE] INFO: Resume Monitor: 3 User ID: 1
2023-10-19T15:51:01-05:00 [MONITOR] INFO: Get Monitor: 3 User ID: 1
2023-10-19T15:51:37-05:00 [MANAGE] INFO: Resume Monitor: 5 User ID: 1
2023-10-19T15:51:37-05:00 [MONITOR] INFO: Added Monitor: undefined User ID: 1
2023-10-19T15:52:01-05:00 [MANAGE] INFO: Resume Monitor: 6 User ID: 1
2023-10-19T15:52:01-05:00 [MONITOR] INFO: Added Monitor: undefined User ID: 1
2023-10-19T15:52:01-05:00 [MONITOR] WARN: Monitor #3 'Kubernetes App Endpoints': Pending: Child inaccessible | Max retries: 1 | Retry: 0 | Retry Interval: 60 seconds | Type: group
nneul commented 11 months ago

It didn't happen a second time, so it may be a race condition / timing of when uptime kuma aggregates results or something.

torbengb commented 4 months ago

This still happens. I have a new installation (Version: 1.23.13) and this happens every time. If you don't see it, just try again.