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

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

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

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

研究方向

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.

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

描述

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.

主要語言
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 摘要。