summaryrefslogtreecommitdiffstats
path: root/streaming
diff options
context:
space:
mode:
authorChris Akritidis <43294513+cakrit@users.noreply.github.com>2018-12-31 13:11:46 +0100
committerGitHub <noreply@github.com>2018-12-31 13:11:46 +0100
commit9fe0a36ed8a22fa974cb2adf72c31dd0c4e870ba (patch)
treec6a4426a691b316249b1e577bc247534f11dfd20 /streaming
parent31dc2e9761ab404b13655aa174cff726dc63d03a (diff)
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
Diffstat (limited to 'streaming')
-rw-r--r--streaming/README.md9
1 files changed, 5 insertions, 4 deletions
diff --git a/streaming/README.md b/streaming/README.md
index 5956915a8c..3ca1bfdbcb 100644
--- a/streaming/README.md
+++ b/streaming/README.md
@@ -18,8 +18,9 @@ a netdata performs:
Local netdata (`slave`), **without any database or alarms**, collects metrics and sends them to
another netdata (`master`).
-The user can take the full functionality of the `slave` netdata at
-http://master.ip:19999/host/slave.hostname/. Alarms for the `slave` are served by the `master`.
+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/.
+
+Alarms for the `slave` are served by the `master`.
In this mode the `slave` is just a plain data collector.
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`.
Local netdata (`slave`), **with a local database (and possibly alarms)**, collects metrics and
sends them to another netdata (`master`).
-The user can use all the functions **at both** http://slave.ip:19999/ and
-http://master.ip:19999/host/slave.hostname/.
+The user can use all the functions **at both** http://slave-ip:slave-port/ and
+http://master-host:master-port/host/slave-host/.
The `slave` and the `master` may have different data retention policies for the same metrics.