Change instruction to reload HEALTH (#9869)
Add netdatacli as instruction to reload health.
thiagoftsm committed
Sep 10, 2020 at 13:10 UTC
f57c6c0df9112a43bb13416d3368c6de4105699e
3 files changed
+11
-9
docs/guides/monitor/stop-notifications-alarms.md
+2
-2
@@ -72,8 +72,8 @@ To silence this alarm, change `sysadmin` to `silent`.
72
to: silent
73
```
74
75
-Use `killall -USR2 netdata` to reload your health configuration and ensure you get no more notifications about that
76
-alarm.
75
+Use one of the available [methods](/health/QUICKSTART.md#reload-health-configuration) to reload your health configuration
76
+ and ensure you get no more notifications about that alarm**.
77
78
You can add `to: silent` to any alarm you'd rather not bother you with notifications.
79
docs/guides/step-by-step/step-05.md
+2
-6
@@ -70,11 +70,7 @@ the `warn` and `crit` lines to the values of your choosing. For example:
70
```
71
72
You _can_ [restart Netdata](/docs/getting-started.md#start-stop-and-restart-netdata) to enable your tune, but you can
73
-also send a signal to Netdata to reload _only_ the health monitoring component.
74
-
75
-```bash
76
-killall -USR2 netdata
77
-```
73
+also reload _only_ the health monitoring component using one of the available [methods](/health/QUICKSTART.md#reload-health-configuration).
74
75
You can also tune any other aspect of the default alarms. To better understand how each line in a health entity works,
76
read our [health documentation](/health/README.md).
@@ -106,7 +102,7 @@ To silence this alarm, change `sysadmin` to `silent`.
102
to: silent
103
```
104
109
-Use `killall -USR2 netdata` to reload your health configuration. You can add `to: silent` to any alarm you'd rather not
105
+Use `netdatacli reload-health` to reload your health configuration. You can add `to: silent` to any alarm you'd rather not
106
bother you with notifications.
107
108
## Write your first health entity
health/QUICKSTART.md
+7
-1
@@ -125,9 +125,15 @@ To make any changes to your health configuration live, you must reload Netdata's
125
without restarting all of Netdata, run the following:
126
127
```bash
128
-killall -USR2 netdata
128
+netdatacli reload-health
129
```
130
131
+If you receive an error like `command not found`, this means that `netdatacli` is not installed in your `$PATH`. In that
132
+ case, you can reload only the health component by sending a `SIGUSR2` to Netdata:
133
+
134
+```bash
135
+killall -USR2 netdata
136
+```
137
## What's next?
138
139
To learn about all of Netdata's health configuration options, view the [reference guide](/health/REFERENCE.md) and