Update streaming documentation and config file with more info on how health enabled by default = auto works. (#6281)
Chris Akritidis committed
Jun 14, 2019 at 12:36 UTC
924c18b1732a84f69bc4a588064c666ae842ddac
2 files changed
+6
-1
streaming/README.md
+4
@@ -342,6 +342,10 @@ If you used many API keys, you can add one such section for each API key.
342
343
When done, restart netdata on the `master` node. It is now ready to receive metrics.
344
345
+Note that `health enabled by default = auto` will still trigger `last_collected` alarms, if a connected slave does not exit gracefully. If the netdata running on the slave is
346
+stopped, it will close the connection to the master, ensuring that no `last_collected` alarms are triggered. For example, a proper container restart would first terminate
347
+the netdata process, but a system power issue would leave the connection open on the master side. In the second case, you will still receive alarms.
348
+
349
#### Configuring the `slaves`
350
351
On each of the slaves, edit `/etc/netdata/stream.conf` (to edit it on your system run `/etc/netdata/edit-config stream.conf`) and set these:
streaming/stream.conf
+2
-1
@@ -125,7 +125,8 @@
125
# 3 possible values:
126
# yes enable alarms
127
# no do not enable alarms
128
- # auto enable alarms, only when the sending netdata is connected
128
+ # auto enable alarms, only when the sending netdata is connected. For ephemeral slaves or slave system restarts,
129
+ # ensure that the netdata process on the slave is gracefully stopped, to prevent invalid last_collected alarms
130
# You can also set it per host, below.
131
# The default is taken from [health].enabled of netdata.conf
132
health enabled by default = auto