louislam/uptime-kuma
View on GitHubPausing a group does not pause the individual monitors of that group
Open
#7242 opened on Apr 4, 2026
A:dashboardfeature-requestgood first issuehelp wanted
Description
📑 I have found these related issues/pull requests
I could not find related issues.
🛡️ Security Policy
- I have read and agree to Uptime Kuma's Security Policy.
📝 Description
I have a group that contains monitors for virtual machines.
- I pause the whole group
- Kill all virtual machines for updates
- Uptime kuma starts sending alerts that the individual VMs are down
- Group appears paused, but not the individual VMs under that group
👟 Reproduction steps
- Pause a group
- Kill the systems under the group
- See that uptime kuma complains about the killed systems
👀 Expected behavior
I expect all monitors under the group to be paused as well.
😓 Actual Behavior
Alerts about killed VMs.
🐻 Uptime-Kuma Version
2.2.1
💻 Operating System and Arch
AlmaLinux 10 with Docker
🌐 Browser
Firefox 149
🖥️ Deployment Environment
- Runtime Environment:
- Docker: Version
29.3.1(ce edition) - Docker Compose: Version
5.1.1
- Docker: Version
- Database:
- No idea, whatever came with the docker container?
- Database Storage:
- Filesystem:
- Linux: ext4
- Storage Medium: NVMe
- Filesystem:
- Uptime Kuma Setup:
- Number of monitors:
18
- Number of monitors:
📝 Relevant log output