mirror of
https://github.com/prometheus/prometheus
synced 2024-12-28 09:42:22 +00:00
docs: Add signal information to getting started
Closes prometheus/docs#167 Signed-off-by: Harold Dost <h.dost@criteo.com>
This commit is contained in:
parent
d437f0bb6b
commit
3125e169ae
@ -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 <PID>`, replacing `<PID>` 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 <PID>`, replacing `<PID>` with your Prometheus process ID.
|
||||
|
Loading…
Reference in New Issue
Block a user