Thanks all for all the options where we can easily reload the updated configurations.
That does mean, we should not restart the service, if we restart the issues I have mentioned in the email are expected? On Mon, Mar 16, 2020 at 1:15 AM Cameron Kerr <[email protected]> wrote: > In a similar vien, I use the following for prometheus running in a docker > container (where prometheus is PID 1) > > sudo docker exec monitoring_prometheus_1 kill -HUP 1 > > (where monitoring_prometheus_1 is the name given to the docker container) > > On Monday, 16 March 2020 21:03:53 UTC+13, Brian Candler wrote: >> >> And a third option (for picking up changes after modifying config files) >> is even simpler: >> >> killall -HUP prometheus >> >> -- > 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/f342b026-5222-4e9e-8fdd-b496d1e650c4%40googlegroups.com > <https://groups.google.com/d/msgid/prometheus-users/f342b026-5222-4e9e-8fdd-b496d1e650c4%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAPs_AfgYShpVP93GRsx%3DBOz2cz4MX4s%3DxWRvMWcSHTw1pr3jHg%40mail.gmail.com.
