| 1 | # Registry |
| 2 | |
| 3 | Netdata uses a **central Registry**. Together with certain browser features, it allows for unified cross-Agent dashboards. For example, when you jump from Agent to Agent using the node menu, several session settings (like the currently viewed charts, the current zoom and pan operations on the charts, etc.) are propagated to the new Agent, so that the new dashboard will come with exactly the same view. |
| 4 | |
| 5 | ## Default Registry |
| 6 | |
| 7 | The default Registry is `https://registry.my-netdata.io`, which is currently served by `https://london.my-netdata.io`. This Registry listens to both HTTP and HTTPS requests with the default being HTTPS. |
| 8 | |
| 9 | ## What data is stored |
| 10 | |
| 11 | The Registry keeps track of four entities: |
| 12 | |
| 13 | 1. **machines**: The Netdata installations (a random GUID generated by each Netdata the first time it starts, we call this **machine_guid**) |
| 14 | |
| 15 | For each Netdata installation, the Registry keeps track of the various different URLs it has accessed. |
| 16 | |
| 17 | 2. **people**: 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**) |
| 18 | |
| 19 | For each person, the Registry keeps track of the Netdata installations it has accessed and their URLs. |
| 20 | |
| 21 | 3. **URLs** of Netdata installations (as seen by the web browsers) |
| 22 | |
| 23 | For each URL, the Registry keeps the URL and nothing more. Each URL is linked to **people** and **machines**. The only way to find a URL is to know its **machine_guid** or have a **person_guid** that is linked to it. |
| 24 | |
| 25 | 4. **accounts**: The information used to sign in via one of the available sign-in methods. Depending on the method, this may include only an email or additionally a profile picture or avatar. |
| 26 | |
| 27 | For **people**, **accounts** and **machines**, the Registry keeps links to **URLs**, each link with two timestamps (first time seen, last time seen) and a counter (number of times it has been seen). |
| 28 | |
| 29 | **machines**, **people** and timestamps are stored in the Netdata Registry regardless of whether you sign in or not. |
| 30 | |
| 31 | ## Communication with the Registry |
| 32 | |
| 33 | **Only** your web browser communicates with the Registry. If sending this information is against your policies, you can [run your own Registry](/src/registry/CONFIGURATION.md) |
| 34 | |
| 35 | Your Agents do not talk to the Registry. This is a diagram explaining the process: |
| 36 | |
| 37 | ```mermaid |
| 38 | sequenceDiagram |
| 39 | participant WebBrowser as Web Browser |
| 40 | participant Netdata1 as Netdata 1 |
| 41 | participant Registry1 as Registry 1 |
| 42 | |
| 43 | WebBrowser->>Netdata1: 1. Hi, give me the dashboard |
| 44 | Netdata1-->>WebBrowser: 2. Welcome, here it is... |
| 45 | Note over WebBrowser,Netdata1: a few seconds later |
| 46 | |
| 47 | WebBrowser->>Netdata1: 3. Now give me the Registry information |
| 48 | Netdata1-->>WebBrowser: 4. Here it is, talk to Registry 1 |
| 49 | |
| 50 | WebBrowser->>Registry1: 5. Hey Registry 1, I am accessing Netdata 1... |
| 51 | Registry1-->>WebBrowser: 6. Nice! Here are other Netdata Agents you have accessed in the past |
| 52 | |
| 53 | Note over WebBrowser: Only your web browser talks to the Registry |
| 54 | ``` |