diff options
| author | Chris Akritidis <43294513+cakrit@users.noreply.github.com> | 2019-06-14 12:36:38 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-06-14 12:36:38 +0200 |
| commit | 924c18b1732a84f69bc4a588064c666ae842ddac (patch) | |
| tree | d48089816dbcc1821e5de0cc4172dc3f112f1ff2 /streaming/README.md | |
| parent | dc473edb73224905c2f74ae5d409e2fd13511197 (diff) | |
Update streaming documentation and config file with more info on how health enabled by default = auto works. (#6281)
Diffstat (limited to 'streaming/README.md')
| -rw-r--r-- | streaming/README.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/streaming/README.md b/streaming/README.md index e5c35fc7e7..c7a3d28983 100644 --- a/streaming/README.md +++ b/streaming/README.md @@ -342,6 +342,10 @@ If you used many API keys, you can add one such section for each API key. When done, restart netdata on the `master` node. It is now ready to receive metrics. +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 +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 +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. + #### Configuring the `slaves` 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: |