Hello,

We have a particular alert where we would like to configure a different 
repeat_interval? What is the best practice for doing this?

One option would be to duplicate our existing routing tree, and just change 
the repeat_interval. Then we could route to this based on the alert name. 
The downside of is the alert name needs to be kept in sync between the 
alert rule config and the Alertmanager config.

To overcome this problem we could be to add a label to the alert definition 
which specifies the repeat_interval, then we can route these to the 
appropriate Alertmanager routing tree.

Is it possible to dynamically set the repeat_interval dynamically in the 
Alertmanager config? I assume not, in which case we are still left with the 
problem of needing to duplicate the routing trees in Alertmanager for each 
repeat_interval value.

What are your thoughts on these approaches? Are there alternative solutions 
I might have missed?

Many thanks!

-- 


--

*This email is confidential and protected by copyright, and might 
contain privileged information. The same goes for any attachments.*
*
*
*If 
we’ve sent it to you by mistake (sorry), please don’t copy it or show it to 
anyone. You also shouldn’t use it to make a decision, and you shouldn’t 
rely on the contents.  Let the sender know as soon as you can, and then 
delete the email. Thank you!*



Monzo Bank Limited is a company registered 
in England and Wales (No. 09446231) registered at Broadwalk House, 5 Appold 
St, London, EC2A 2AG. Monzo Bank Ltd is authorised by the Prudential 
Regulation Authority (PRA) and regulated by the Financial Conduct Authority 
and the PRA. Our Financial Services Register number is 730427.

-- 
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/49ec8fad-b468-40bb-97df-d3fcee4b68d8n%40googlegroups.com.

Reply via email to