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

未關閉
#3,578 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
25/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
clickhouse, typescript
領域
observability

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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

主要語言
TypeScript
星號
10.1k
分支
527
平均合併
1 天 20 小時
30 天內合併 PR
186

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

ClickHouse/ClickStack 的其他 Issue

查看 ClickHouse/ClickStack 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。