From 3125e169ae46b909f5fadb235c47ae8bd6e04a7f Mon Sep 17 00:00:00 2001 From: Harold Dost Date: Tue, 17 May 2022 11:49:54 +0200 Subject: [PATCH] docs: Add signal information to getting started Closes prometheus/docs#167 Signed-off-by: Harold Dost --- docs/getting_started.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/getting_started.md b/docs/getting_started.md index 028b1c86f..11d8d0fb8 100644 --- a/docs/getting_started.md +++ b/docs/getting_started.md @@ -250,3 +250,18 @@ scrape_configs: Restart Prometheus with the new configuration and verify that a new time series with the metric name `job_instance_mode:node_cpu_seconds:avg_rate5m` is now available by querying it through the expression browser or graphing it. + +## Reloading configuration + +As mentioned in the [configuration documentation](configuration/configuration.md) a +Prometheus instance can have its configuration reloaded without restarting the +process by using the `SIGHUP` signal. If you're running on Linux this can be +performed by using `kill -s SIGHUP `, replacing `` with your Prometheus +process ID. + +## Shutting down your instance gracefully. + +While Prometheus does have recovery mechanisms in the case that there is an +abrupt process failure it is recommend to use the `SIGTERM` signal to cleanly +shutdown a Prometheus instance. If you're running on Linux this can be performed +by using `kill -s SIGHUP `, replacing `` with your Prometheus process ID.