diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2019-02-08 07:31:03 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2019-02-08 07:31:03 +0000 |
| commit | 50485bedfd9818165aa1d039d0abe95a559134b7 (patch) | |
| tree | 79c7b08f67edcfb0c936e7a22931653b91189b9f /registry/README.md | |
| parent | Releasing debian version 1.11.1+dfsg-7. (diff) | |
| download | netdata-50485bedfd9818165aa1d039d0abe95a559134b7.tar.xz netdata-50485bedfd9818165aa1d039d0abe95a559134b7.zip | |
Merging upstream version 1.12.0.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to '')
| -rw-r--r-- | registry/README.md | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/registry/README.md b/registry/README.md index de24b301..5a9a2b3b 100644 --- a/registry/README.md +++ b/registry/README.md @@ -1,4 +1,4 @@ -# Netdata registry +# Registry Netdata registry implements the `my-netdata` menu on netdata dashboards. The `my-netdata` menu lists the netdata servers you have visited. @@ -36,23 +36,23 @@ The registry keeps track of 3 entities: For each netdata installation (each `machine_guid`) the registry keeps track of the different URLs it is accessed. -1. **persons**: i.e. the web browsers accessing the netdata installations (a random GUID generated by the registry the first time it sees a new web browser; we call this **person_guid**) +2. **persons**: i.e. the web browsers accessing the netdata installations (a random GUID generated by the registry the first time it sees a new web browser; we call this **person_guid**) For each person, the registry keeps track of the netdata installations it has accessed and their URLs. -1. **URLs** of netdata installations (as seen by the web browsers) +3. **URLs** of netdata installations (as seen by the web browsers) For each URL, the registry keeps the URL and nothing more. Each URL is linked to *persons* and *machines*. The only way to find a URL is to know its **machine_guid** or have a **person_guid** it is linked to it. ## Who talks to the registry? -Your web browser **only**! Check here if this is against your policies: [how to not send any information to a thirdparty server](../doc/netdata-security.md#netdata-security) +Your web browser **only**! If sending this information is against your policies, you can [run your own registry](#run-your-own-registry) Your netdata servers do not talk to the registry. This is a UML diagram of its operation:  -## What data the registry maintains? +## What data does the registry store? Its database contains: @@ -72,9 +72,9 @@ Yeap! The registry can handle 50.000 - 100.000 requests **per second per core** We believe, it can do it... -## Every netdata can be a registry +## Run your own registry -Yes, you read correct, **every netdata can be a registry**. Just pick one and configure it. +**Every netdata can be a registry**. Just pick one and configure it. **To turn any netdata into a registry**, edit `/etc/netdata/netdata.conf` and set: @@ -150,3 +150,5 @@ ERROR 409: Cannot ACCESS netdata registry: https://registry.my-netdata.io respon ``` This error is printed on your web browser console (press F12 on your browser to see it). + +[]() |