Delay between Probe and Monitoring Log / Incident #472

Closed
opened 2026-04-05 16:19:57 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @Vincent-Bouffard-Ouidou on 5/25/2025

Describe the bug
Over time, the delay increases between what probe detect and when the monitoring logs are displayed.
For example, i'm monitoring my self-hosted Gitlab.
I've stopped the registry, probes (1 and 2) have detected that the status was 502, but nothing in monitoring logs or in incidents.
It was May 25 2025, 23:20 CEST but the latest log in monitoring logs is May 25 2025, 19:16 CEST
The incident was created about 5 hours after the downtime.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Monitoring Logs'
  2. Click on 'View Summary'
  3. See delay

Expected behavior
See in column "Monitored At" the latest monitor summary with no delay
Incident is created as soon as it's detected

Deployment Type
Self-hosted : 7.0.4255

Additional context
I have about 100 monitored, all website and ports are configured with an interval of 5 minutes.
The other monitors (SSL certificate) are configured with an interval of every day.
I have the feeling that clickhouse cannot process information in real time and it piles up over time.

It was working well to 7.0.3980, but after, i'm not sure.

*Originally created by @Vincent-Bouffard-Ouidou on 5/25/2025* **Describe the bug** Over time, the delay increases between what probe detect and when the monitoring logs are displayed. For example, i'm monitoring my self-hosted Gitlab. I've stopped the registry, probes (1 and 2) have detected that the status was 502, but nothing in monitoring logs or in incidents. It was May 25 2025, 23:20 CEST but the latest log in monitoring logs is May 25 2025, 19:16 CEST The incident was created about 5 hours after the downtime. **To Reproduce** Steps to reproduce the behavior: 1. Go to 'Monitoring Logs' 2. Click on 'View Summary' 3. See delay **Expected behavior** See in column "Monitored At" the latest monitor summary with no delay Incident is created as soon as it's detected **Deployment Type** Self-hosted : 7.0.4255 **Additional context** I have about 100 monitored, all website and ports are configured with an interval of 5 minutes. The other monitors (SSL certificate) are configured with an interval of every day. I have the feeling that clickhouse cannot process information in real time and it piles up over time. It was working well to 7.0.3980, but after, i'm not sure.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#472