Skip to content
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

The group monitor is not functioning correctly and shows inaccurate counts. #5366

Closed
1 task done
Chris-sentbe opened this issue Nov 21, 2024 · 3 comments
Closed
1 task done
Labels
bug Something isn't working

Comments

@Chris-sentbe
Copy link

πŸ“‘ I have found these related issues/pull requests

nothing reported

πŸ›‘οΈ Security Policy

Description

ν™”λ©΄ 캑처 2024-11-21 174907
ν™”λ©΄ 캑처 2024-11-21 175018
ν™”λ©΄ 캑처 2024-11-21 182147

πŸ‘Ÿ Reproduction steps

When I create a Test Group and assign Test Cases under it, the results marked as "offline" are not being counted in the Group.

πŸ‘€ Expected behavior

The Offline values of the cases under the Group should be accurately reflected in the Group's SLA results.

πŸ˜“ Actual Behavior

The test results under the Group are sometimes reflected in the Group's SLA results and sometimes not.

This issue particularly occurs when there is a short Offline period followed by recovery.

Could this be related to the heartbeat of the monitor group?

I believed the monitor group should contain all Offline status of its sub-items.

🐻 Uptime-Kuma Version

2.0.0 beta

πŸ’» Operating System and Arch

amazon linux 2023 6.1.109-118.189

🌐 Browser

Chrome 130.0.6723.119

πŸ–₯️ Deployment Environment

  • Runtime: Docker 25.0.6
  • Database: sqlite
  • Filesystem used to store the database on: AWS EBS XFS on a ssd
  • number of monitors: 16

πŸ“ Relevant log output

nothing speical in a docker logs
@Chris-sentbe Chris-sentbe added the bug Something isn't working label Nov 21, 2024
@CommanderStorm
Copy link
Collaborator

On what schedule have you set the group monitor to check the contained statues compared to the schedule of the statuses?

@Chris-sentbe
Copy link
Author

제λͺ© μ—†μŒ it is all same

@Chris-sentbe
Copy link
Author

It seems that "Group" does not check if a local item recovers within 20 seconds. Very brief interruptions are not included in the SLA, so it might not be considered a bug. Instead, I'll need to request a feature enhancement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants