missed evaluation in raw SQL alerts compare multi-window results to a single window threshold

Abierto
#3,578 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
clickhouse, typescript

Línea de trabajo

A reproducing test case is linked in PR #3577; start by reading that test and tracing the raw SQL Number tile alert evaluation path it exercises. Compare how the extended date range is handled for raw SQL alerts versus builder and time-series alerts. Done means a missed evaluation does not make the combined multi-window result breach a threshold intended for one window; verify with a regression test covering the stated example.

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

Descripción

bug Needs Feedback

What happened?

After a missed alert evaluation the next run's date range is extended back to the last evaluated window. Builder and time-series alerts split that range into one bucket per interval and compare each bucket to the threshold. Raw SQL Number tile alerts run their SQL once over the whole extended range and compare that one result to the threshold, which is meant for a single window.

Say you have 2 errors per window and your threshold is 3, a missed evaluation will result in an alert in the next eval even though the threshold was never actually breached

Steps to reproduce

Reproduces on play.hyperdx.io?
Reproduced on a test case in this PR: https://github.com/hyperdxio/hyperdx/pull/3577

How are you running HyperDX?

Where does it show up?

Debug info

(paste Help → Copy debug info here)

Logs

Lenguaje dominante
TypeScript
Estrellas
10.1k
Forks
527
Merge medio
1 d 20 h
PR fusionados (30 d)
186

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 ClickHouse/ClickStack

Todos los issues de ClickHouse/ClickStack

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.