We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
感谢作者简洁清晰的解释了 gossip 协议如何实现了多个 alertmanager 实例对来自相同 prometheus 实例的报警进行去重~~ 建议对 fullmesh 结构下 alertmanager 是如何对来自不同 prometheus 实例的相同报警进行去重的提及一下,即:"alertmanager 判定两个指标一致的前提是所有 label 完全一致" ;之所以增加这个描述是因为通常互为备份的两个 prometheus 会设置 external_labels 对 metrics 来源进行标记(尤其是在使用 remote write 时避免冲突),在这种场景下就需要配置alert_relabel_configs将不一致的 label 重置为一致再发送到 alertmanager
相关讨论以及解释见: prometheus/alertmanager#1448 https://www.robustperception.io/high-availability-prometheus-alerting-and-notification
补充这部分内容可以有助于原理表述的完整性,仅供参考 :D
The text was updated successfully, but these errors were encountered:
No branches or pull requests
感谢作者简洁清晰的解释了 gossip 协议如何实现了多个 alertmanager 实例对来自相同 prometheus 实例的报警进行去重~~
建议对 fullmesh 结构下 alertmanager 是如何对来自不同 prometheus 实例的相同报警进行去重的提及一下,即:"alertmanager 判定两个指标一致的前提是所有 label 完全一致" ;之所以增加这个描述是因为通常互为备份的两个 prometheus 会设置 external_labels 对 metrics 来源进行标记(尤其是在使用 remote write 时避免冲突),在这种场景下就需要配置alert_relabel_configs将不一致的 label 重置为一致再发送到 alertmanager
相关讨论以及解释见:
prometheus/alertmanager#1448
https://www.robustperception.io/high-availability-prometheus-alerting-and-notification
补充这部分内容可以有助于原理表述的完整性,仅供参考 :D
The text was updated successfully, but these errors were encountered: