Hello, I am jorik

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

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
25/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
helm, kubernetes, mongodb, typescript

研究方向

Start with the file-based dashboard provisioner and PR #3233, then read createOrUpdateDashboardAlerts and validateAlertInput, which the issue identifies as the existing alert paths. Done means provisioned tile alerts are created or updated, invalid alerts are skipped with a warning while retaining the last valid version, removed tile alerts are deleted, and app-created alerts remain unaffected.

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

描述

external

Tell us a bit about yourself before your first pull request. A couple of sentences is plenty.

Who are you?

Jorik (@jorik), a full-stack .NET developer. We run ClickStack on AKS through its Helm chart and keep our HyperDX dashboards in git with the file-based dashboard provisioner from #1962, which I really like.

What would you like to work on?

The same for alerts. The provisioner accepts a tile's config.alert (it passes DashboardWithoutIdSchema), but it writes tiles straight to Mongo and never creates the alert, so a provisioned alert validates and never fires.

https://github.com/hyperdxio/hyperdx/pull/3233 makes the provisioner create and update tile alerts through the existing createOrUpdateDashboardAlerts, after checking each one with validateAlertInput like the alerts API does. Alerts it creates are flagged provisioned: true and deleted once their tile no longer declares one. An invalid alert is skipped with a warning and keeps its last valid version, and alerts created in the app are left alone.

Anything we can help with?

A /vouch @jorik so #3233 can be reviewed, and a steer on whether provisioned alerts should replace an app-created alert on the same tile (what the PR does now) or leave it.

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