I don’t know the exact setup of the helm chart, but generally those use cases are covered by the prometheus operator. The first by provisioning PrometheusRule objects in the application namespace and the second, Prometheus is simply automatically reloaded when the new rule appears in the container, which because of configmap reload times, this can be up to 5minutes delay.
I recommend going through the alerting user guide to understand the components involved: https://github.com/coreos/prometheus-operator/blob/master/Documentation/user-guides/alerting.md On Sun 22. Mar 2020 at 23:41, EnthuDeveloper <[email protected]> wrote: > Hello, > I am trying helm charts(prometheus operator ) to install Prometheus and > Alertmanager. Looking for some recommendations as to what the preferable > options are for : > 1. Reading alert rules generated from our application in form of a yaml > file and loading them to container running Prometheus ? > 2. How to reload the alert rules for prometheus in case , the rules yaml > file generated by our application sees any modifications. > > Any recommendations would be much appreciated ? > > Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "Prometheus Developers" 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-developers/f81e52b7-d5bc-4c2f-8543-2b626956e92a%40googlegroups.com > . > -- You received this message because you are subscribed to the Google Groups "Prometheus Developers" 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-developers/CAOs1Umx5aEsiNQx2KrDZjK6w55e6-TE20qJkM%3Daf3thG_eqBTg%40mail.gmail.com.
