Project

General

Profile

Documentation #52577

alertmanager configuration prevents users from adding their own escalation process

Added by Paul Cuzner over 2 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
cephadm/monitoring
Target version:
% Done:

0%

Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

cephadm manages the alertmanager.yml file, and regenerates it during a reconfig overriding any local changes made.

Out of the box cephadm configures alertmanager to pass alerts to the UI - but this doesn't really align with typical ops teams. Ideally, the user should be able to add their own receiver definitions (slack, email, pagerduty etc) and not have them regressed by cephadm.

History

#2 Updated by Paul Cuzner over 2 years ago

I think this is potentially a doc task. As you point out the webhooks integration is there, but things like slack etc aren't covered by that. So perhaps a PR against the docs to show an example of patching the template to include a slack config would suffice to provide a simple way to ensure the integration 'sticks'?

#3 Updated by Sebastian Wagner over 2 years ago

  • Tracker changed from Feature to Documentation

Also available in: Atom PDF