On 2020-06-04 14:57, Vikrant Chaudhary wrote:
This may be a basic use case but I couldn't figure out based on the
documentation I looked at.
I am expecting each of my service to create some service level alerts
and package them as part of their helm charts which seems simple
enough to do - each service creates a Prometheus rule for alerts it
cares about.
Here is my question - Is it possible for the service to allow
implementing some of the routing rules as part of its deployment
definition ?
To me it seems like there is one config file where alert manager picks
the routing information from. How can individual services update that
config file (basically a configmap in a secret in k8s) as part of
their deployment definition ?
You wouldn't generally expect Alertmanager routing rules to be services
specific, and equally are likely to vary depending on the setup of the
end user - they might choose different things to send to Slack or might
use Teams instead, etc.
You'd normally have some labels/annotations set by the alert detailing
some sort of severity, then the routing rules would match on those and
determin where an alert is sent.
--
Stuart Clark
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/2b83fa28fbb334b051b16c6cf01a7640%40Jahingo.com.
