And a third option (for picking up changes after modifying config files) is even simpler:
killall -HUP prometheus This doesn't require setting any config flags. If there's a problem with your configs, prometheus will keep running with the old ones. You can check for errors in the error output, e.g. under systemd it would be "journalctl -eu prometheus" Another useful command is: promtool check config /path/to/prometheus.yaml which can be used to check whether your new config and rules are valid *before* you send the reload signal. -- 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/f2554a4e-f7cf-426a-89db-f684e1063924%40googlegroups.com.
