Open nneul opened 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.
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.
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
Description
👟 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