There is no monitoring

[yanXiaoi]

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

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

When it has been running normally for a while, it does not check the item and no data appears

And it is normal in the state

As shown in the picture, it stopped checking on the 27th

👟 Reproduction steps

A large number of monitoring cases, occasionally stopping one or two monitoring

👀 Expected behavior

Normal monitoring

😓 Actual Behavior

There is no monitoring

🐻 Uptime-Kuma Version

1.19.6

💻 Operating System and Arch

Centos 7.9

🌐 Browser

Edge 110.0.1587.41

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[chenshaoju]

Sorry for my English.

I have the same issue with specific monitoring items.

here is a screen recording of this issue:

Output_QP.mp4

here are uptime-kuma logs from docker:
_uptime-kuma_logs.txt

This issue may have the same at: #736

Uptime Kuma Version: 1.22.1

Docker Version: Standalone 24.0.5

If need any more information, please don't hesitate to ask.👏

[CommanderStorm]

@yanXiaoi @chenshaoju
How many monitors do you have, what type are they, and what storage are you running on?
Could you try 1.23.0-beta.1?
A few performance/stability fixes (#2800 #3380 #3174) have gone into this release making higher numbers of monitors more feasible, more are planned for the v2.0-release.

[chenshaoju]

Thanks for the reply, I have 53 items running, on a Debian 12 system with docker, in a SATA SSD, Not using network mounts or something.

I try using the beta version, but I don't know how to upgrade in docker, I'm a docker noob, sorry. :/

I can be waiting for the 1.23.0 to release and upgrade in docker later.

If this issue is fixed, I will update the post. 👏

[chenshaoju]

@CommanderStorm After update to 1.23.0, this issue looks has been fixed.

Thanks! 🍻

[medram]

I'm having the same issue.

[CommanderStorm]

@medram there currently is not enough content in this issue to debug on

Large deployments (think above 300-400 monitors, less if using more demanding monitors like "real browser") are not supported in the v1 of uptime kuma.

The upcoming v2 release does include a number of performance updates, which should™️ resolve a bunch of perfomance issue with large deployments.
See https://github.com/louislam/uptime-kuma/milestone/24 for the progress

[chakflying]

Fixed by #3952.