Feature Request: Define Alerts Using YAML

未關閉
#2,917 2 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@wrn14897 已經在處理了。

開始於 2026年8月18日。

評估

這個 Issue 還沒有評估資料。

描述

external

Feature Request: Define Alerts Using YAML

Currently, alerts have to be configured manually through the HyperDX UI. This works for a few services, but when there are many services and APIs, creating and maintaining alerts for each one becomes repetitive and difficult.

It would be useful to support defining alerts in a YAML file alongside the service code:

alerts:
  - name: service-a-api-errors
    service: service-a
    api: /api/orders
    threshold: 10
    window: 5m

  - name: service-b-api-latency
    service: service-b
    api: /api/users
    threshold: 2000
    window: 5m

HyperDX could then provide a way to consume this YAML — through an upload option, API, CLI, or CI/CD integration — and automatically create/update the corresponding alerts.

This would make alerts version-controlled, reproducible, and much easier to manage across multiple services and environments.

Instead of manually setting up alerts for every API in the UI, define them once in YAML alongside the code and let HyperDX provision them automatically.

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