Send repeated and resolved Slack notifications in the original alert thread

未关闭
#3,439 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

Start by tracing how HyperDX sends Slack alert notifications and how it represents firing, repeated, and resolved states; the issue does not name specific files or tests. Compare the flow with the linked Alertmanager implementation. Done means repeated and resolved notifications appear in the original message's thread, while a firing after recovery starts a new thread.

由索引模型根据 Issue 内容生成。

描述

alerting enhancement external Needs Feedback

What are you trying to do?

We use HyperDX alerts with Slack notifications. Repeated and resolved notifications appear as separate messages, making it hard to follow the same alert and cluttering the channel.

What would you like to see?

An option to post the first notification to the channel and send repeated and resolved notifications in that message's thread.

A new firing after recovery should start a new thread.

Alternatives you've considered

Forwarding alerts through another tool or a custom webhook service, but native support would avoid running an additional component.

Anything else?

Alertmanager has a similar implementation:
https://github.com/prometheus/alertmanager/pull/5540

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