Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Alerts are sometimes not being fired when the logs meet the threshold criteria.

Aperta
  • Qualcosa non va?
#3,307 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
57/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
clickhouse, typescript
Ambito
observability

Direzione di ricerca

Start by reading packages/api/src/tasks/checkAlerts/index.ts, especially getScheduledWindowStart, and compare the current Start offset behavior with the tooltip’s promise of delaying evaluation for ingestion lag. Confirm the intended window semantics and add or run tests for a 2-minute offset on a 5-minute interval; done means delayed evaluation checks the intended earlier window and alerts are not missed due to ingestion lag.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug external Needs Feedback

What happened?

Hi, I'm using ClickStack and occasionally run into alerts that are not fired when they should be. This has only happened a few times over the past couple of months.

I think it may be caused by a log arriving after its window has been evaluated -- while investigating I found the Start offset setting under Advanced Settings on the alert, its tooltip says "Delays the start of each evaluation window by this many minutes. Useful when data is ingested with a lag," which sounds like exactly what I need.

However, from reading the source (getScheduledWindowStart in packages/api/src/tasks/checkAlerts/index.ts), I don't think it does this. With a 2 minute offset on a 5 minute interval, it shifts the window to e.g. 09:02:00 AM - 09:07:00 AM, rather than evaluating 09:00:00 AM - 09:05:00 AM two minutes later.

If my understanding is correct, I'm happy to put up a PR so the offset acts as a real evaluation delay for ingestion lag, as the tooltip describes, but wanted to check, can someone confirm the current behaviour isn't intended for a particular use case?

Steps to reproduce

  1. Create a saved query.
  2. Create an alert from that query which fires at >= 1 occurrences per 5-minute window.
  3. Sometimes the alert will not fire.

How are you running HyperDX?

ClickHouse Cloud.

Logs

The log's timestamp is 2026-10-06T23:09:46.990000000Z, which is only about 13 seconds before the window closed, again supporting the theory that it landed after the window was evaluated.

Image

However, the window is completely clear "OK" and no alert was ever sent.

Image

The timestamp on the log is 2026-10-06T23:09:46.990000000Z, so getting "close" to the window.

Lingua principale
TypeScript
Stelle
10k
Fork
494
Merge medio
2g 9h
PR unite (30g)
150

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di hyperdxio/hyperdx

Tutte le issue di hyperdxio/hyperdx

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.