-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
groups with only paused monitors show as UP
instead of PENDING
#4663
Labels
area:monitor
Everything related to monitors
bug
Something isn't working
type:enhance-existing
feature wants to enhance existing monitor
Comments
CommanderStorm
changed the title
Understanding pausing a monitor
groups with only paused monitors show as Apr 10, 2024
UP
instead of PENDING
CommanderStorm
added
bug
Something isn't working
area:monitor
Everything related to monitors
and removed
help
labels
Apr 10, 2024
CommanderStorm
added
the
type:enhance-existing
feature wants to enhance existing monitor
label
Apr 15, 2024
They not only showing up as working the are working, i got notifications of a real downtime with paused monitors. |
Could you screen record how you got into that state? Cannot reproduce this behaviour... |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:monitor
Everything related to monitors
bug
Something isn't working
type:enhance-existing
feature wants to enhance existing monitor
🛡️ Security Policy
📝 Describe your problem
If i pause a https monitor (which is included in a group) i expect that the monitor is fully inactive, the same if i deletet it.
But the heartbeat bar and the graph on dashbord show aktivity and on the Statuspage it looks as active as normal and i even get notifications. So what is actually the intention of pausing? I personally need a kind of deactivation without deleting it fully.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.11
💻 Operating System and Arch
Docker
🌐 Browser
all
🖥️ Deployment Environment
The text was updated successfully, but these errors were encountered: