Slack notifications for inline alerts fail when the chart-explorer link passes Slack's 3000-character block limit

未關閉 適合新手
#3,452 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

@Tyagiquamar 已經在處理了。

開始於 2026年10月25日。

  • #3473 來自 @Tyagiquamar —— 未關閉

評估

難度
2/5
預估耗時
1-3 小時
新手友好度
76/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
typescript

研究方向

先從 packages/api/src/tasks/checkAlerts/transports/slack.ts 開始,檢查 section 區塊如何組合連結、標題和內文;接著閱讀 packages/api/src/tasks/checkAlerts/template.ts,追蹤行內告警連結的建構方式。使用較長的行內告警連結重現故障,並檢查現有的 Slack transport 測試。完成標準是 Slack 接受過長的行內告警通知,同時較短的告警連結仍能正常運作。

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

描述

alerting bug external

Summary

Slack notifications for inline alerts fail when the alert's chart config is large. The alert does fire, but HyperDX records WEBHOOK_ERROR: Failed to send notification to webhook "<name>" and nothing reaches Slack. The same alert set up as a tile alert posts fine.

Cause

For an inline alert, buildAlertMessageTemplateHdxLink (packages/api/src/tasks/checkAlerts/template.ts) links to the chart explorer with the alert's whole chartConfig URL-encoded in the query string (buildChartExplorerLink). Saved-search and tile alerts link to /search/<id> or the dashboard, which are short.

The Slack transport (packages/api/src/tasks/checkAlerts/transports/slack.ts) puts the link, the title and the body into a single section block:

blocks: [{ type: 'section', text: { type: 'mrkdwn', text: `*<${message.hdxLink} | ${message.title}>*\n${message.body}` } }]

Slack limits a section block's text to 3000 characters, and the URL counts toward that limit even though Slack only shows the title. So once the encoded config, the title and the body pass 3000 characters, Slack rejects the message.

Example (HyperDX 2.39.1)

An inline builder alert on a metrics source with 8 histogram series (quantile p99, one metricName each):

  • Each series becomes about 280 characters of the link, because the stored config adds aggCondition, aggConditionLanguage, isDelta and similar fields and URL encoding roughly multiplies JSON by 1.4.
  • With series aliases, a descriptive name and display settings (numberFormat, fitYAxisToData), the link was about 3100 characters. Every notification failed with WEBHOOK_ERROR.
  • After removing the aliases, display settings and most of the name, the link was about 2580 characters and the notification posted.
  • A raw SQL inline alert with about 1700 characters of SQL produces a link of about 2500 characters and is right at the edge.

So a perfectly ordinary alert silently loses its notifications. The only sign is an executionErrors entry on the alert.

Suggestions

Any of these would fix it:

  1. Link inline alerts to something short, for example the alert itself (an alerts page or anchor by alert id), or a server-side stored chart that opens by id, instead of encoding the whole config in the URL.
  2. In the Slack transport, if the section text would pass 3000 characters, fall back to a shorter link (the alerts page) or put the link in a separate block or button. A button url allows up to 3000 characters on its own.
  3. At minimum, warn when saving an inline alert whose notification link would exceed the Slack limit, and say in the WEBHOOK_ERROR that the message was too long.

Environment

  • HyperDX 2.39.1 (ClickStack Helm chart 3.4.0), Slack incoming webhook
  • Alert source: inline (created through the MCP clickstack_save_alert tool / external API)
主要語言
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 摘要。