Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#3,307 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
57/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
clickhouse, typescript
Área
observability

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
10k
Forks
494
Merge medio
2 d 9 h
PR fusionados (30 d)
150

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de hyperdxio/hyperdx

Todos los issues de hyperdxio/hyperdx

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.