Improve instructions on how to view the slave UI (#5083)
##### Summary slave.hostname can be confused with slave.<slave-hostname>. Also added a reference to the fact that slave UIs on the master appear as links on the 'my-netdata' menu ##### Component Name Docs
Chris Akritidis committed
Dec 31, 2018 at 13:11 UTC
9fe0a36ed8a22fa974cb2adf72c31dd0c4e870ba
1 file changed
+5
-4
streaming/README.md
+5
-4
@@ -18,8 +18,9 @@ a netdata performs:
18
Local netdata (`slave`), **without any database or alarms**, collects metrics and sends them to
19
another netdata (`master`).
20
21
-The user can take the full functionality of the `slave` netdata at
22
-http://master.ip:19999/host/slave.hostname/. Alarms for the `slave` are served by the `master`.
21
+The `my-netdata` menu shows a list of all "databases streamed to" the master. Clicking one of those links allows the user to view the full dashboard of the `slave` netdata. The URL has the form http://master-host:master-port/host/slave-host/.
22
+
23
+Alarms for the `slave` are served by the `master`.
24
25
In this mode the `slave` is just a plain data collector.
26
It runs with... **5MB** of RAM (yes, you read correct), spawns all external plugins, but instead
@@ -33,8 +34,8 @@ The same `master` can collect data for any number of `slaves`.
34
Local netdata (`slave`), **with a local database (and possibly alarms)**, collects metrics and
35
sends them to another netdata (`master`).
36
36
-The user can use all the functions **at both** http://slave.ip:19999/ and
37
-http://master.ip:19999/host/slave.hostname/.
37
+The user can use all the functions **at both** http://slave-ip:slave-port/ and
38
+http://master-host:master-port/host/slave-host/.
39
40
The `slave` and the `master` may have different data retention policies for the same metrics.
41