@cryptotaxi247 / netdata-1 / commits / 20eca7288

docs: add comprehensive node states and transitions documentation (#21630)

* docs: add comprehensive node states and transitions documentation Create new authoritative documentation for node states: - Define Live/Stale/Offline/Unseen states with code term mapping - Document two-flag system (liveness + queryable) - Add state transition diagrams and triggers - Document transitions by setup type (standalone, child, vnodes) - Add cleanup thresholds (7 days agents, 48 hours children) - Include configuration reference and comprehensive FAQ Fix existing documentation: - nodes-ephemerality.md: 60 days → 7 days threshold, add Unseen state - node-filter.md: fix 30 days claim, clarify Stale description - remove-node.md: add code terminology mapping - glossary.md: add Live/Stale/Offline/Unseen/Node States entries All docs now link to the new node-states-and-transitions.md as the authoritative reference. * docs: fix MQTT LWT detection timing from ~30s to ~60s The MQTT keepalive interval is 60 seconds (src/aclk/aclk.c:657), not 30 seconds as previously documented. Updated timing in: - Cloud detection mechanism description - Standalone agent transition timing - Child node transition (all parents offline) Verified by cross-referencing with source code. * docs: add backlinks and fix Agent capitalization - Add backlinks to node-states-and-transitions.md from: - nodes-tab.md (Node status filter) - centralized-cloud-notifications-reference.md (unreachable states) - metrics-centralization-points/README.md (See Also) - Fix "agent" → "Agent" for product name consistency (identified by cubic)

Costa Tsaousis committed Jan 24, 2026 at 14:07 UTC 20eca72881b7bc29764ce3ae951e2898fe23492e
8 files changed +317 -7
docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md
+1 -1
@@ -1,6 +1,6 @@
1 # Centralized Cloud Notifications Reference
2
3 -Netdata Cloud sends Alert notifications for nodes in warning, critical, or unreachable states, ensuring Alerts are managed centrally and efficiently.
3 +Netdata Cloud sends Alert notifications for nodes in warning, critical, or [unreachable](/docs/netdata-cloud/node-states-and-transitions.md) states, ensuring Alerts are managed centrally and efficiently.
4
5 ## Benefits of Centralized Notifications
6
docs/dashboards-and-charts/node-filter.md
+4 -2
@@ -7,8 +7,10 @@ Inside the filter, the nodes get categorized into three groups:
7 | Group | Description |
8 |---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
9 | Live | Nodes that are currently online, collecting and streaming metrics to Cloud. Live nodes display raised [Alert](/docs/dashboards-and-charts/alerts-tab.md) counters, [Machine Learning](/src/ml/README.md) availability, and [Functions](/docs/top-monitoring-netdata-functions.md) availability |
10 -| Stale | Nodes that are offline and not streaming metrics to Cloud. Only historical data can be presented from a parent node. For these nodes you can only see their ML status, as they are not online to provide more information |
11 -| Offline | Nodes that are offline, not streaming metrics to Cloud and not available in any parent node. Offline nodes are automatically deleted after 30 days and can also be deleted manually. |
10 +| Stale | Child nodes that stopped streaming to their Parent, but the Parent is still online and has historical data available. For these nodes you can only see their ML status, as they are not online to provide more information |
11 +| Offline | Nodes that are disconnected and have no data available in any Parent. Offline nodes are automatically deleted after a threshold period (7 days for standalone agents, 48 hours for child nodes) and can also be deleted manually. |
12 +
13 +For a complete explanation of node states, transitions, and cleanup rules, see [Node States and Transitions](/docs/netdata-cloud/node-states-and-transitions.md).
14
15 By using the search bar, you can narrow down to specific nodes based on their name.
16
docs/dashboards-and-charts/nodes-tab.md
+1 -1
@@ -15,6 +15,6 @@ All configurations on this page are persistent and visible to all users in the R
15 | **Node row actions** | For each node, you can: <br/>• View status <br/>• Open the single node dashboard <br/>• Access node details via the sidebar <br/>• View active alerts <br/>• Check Machine Learning status <br/>• Check Functions capability status <br/>• Add configuration (beta) <br/>• [Add alert silencing rules](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-alert-notification-silencing-rules.md) <br/>• View key collected attributes |
16 | **Right-hand bar** | Offers additional filtering and information options for the nodes displayed in the center view. |
17 | **Node hierarchy (right bar)** | Displays a hierarchy of the nodes based on the selected ordering, making it easier to locate specific nodes by name. |
18 -| **Filters sub-tab** | Allows filtering of nodes by: <br/>• Host labels <br/>• Node status <br/>• Netdata version <br/>• Individual nodes |
18 +| **Filters sub-tab** | Allows filtering of nodes by: <br/>• Host labels <br/>• [Node status](/docs/netdata-cloud/node-states-and-transitions.md) <br/>• Netdata version <br/>• Individual nodes |
19 | **Alerts sub-tab** | Displays Room alerts and additional details for each alert. |
20 | **Info sub-tab** | Shows detailed node information when you click the info (`i`) icon next to a node's name. |
\ No newline at end of file
docs/glossary.md
+12
@@ -73,6 +73,10 @@ Missing a term? Let us know or submit a request to expand our glossary. Together
73
74 - [**Kubernetes Dashboard** or **Kubernetes Tab**](/docs/dashboards-and-charts/kubernetes-tab.md): Netdata Cloud features enhanced visualizations for the resource utilization of Kubernetes (k8s) clusters, embedded in the default Overview dashboard.
75
76 +## L
77 +
78 +- [**Live** (node state)](/docs/netdata-cloud/node-states-and-transitions.md): A node state in Netdata Cloud indicating the node is actively streaming metrics. Also referred to as "Online" or "Reachable" in code.
79 +
80 ## M
81
82 - [**Metrics Collection**](/src/collectors/README.md): With zero configuration, Netdata auto-detects thousands of data sources upon starting and immediately collects per-second metrics. Netdata can immediately collect metrics from these endpoints thanks to 300+ collectors, which all come pre-installed when you install Netdata.
@@ -96,8 +100,12 @@ Missing a term? Let us know or submit a request to expand our glossary. Together
100
101 - [**Netdata Functions** or **Functions**](/docs/top-monitoring-netdata-functions.md): Routines exposed by a collector on the Netdata Agent that can bring additional information to support troubleshooting or trigger some action to happen on the node itself.
102
103 +- [**Node States**](/docs/netdata-cloud/node-states-and-transitions.md): The connection status of nodes in Netdata Cloud. Nodes can be Live (actively streaming), Stale (not streaming but historical data available via Parent), Offline (disconnected, no data available), or Unseen (claimed but never connected). See [Node States and Transitions](/docs/netdata-cloud/node-states-and-transitions.md).
104 +
105 ## O
106
107 +- [**Offline** (node state)](/docs/netdata-cloud/node-states-and-transitions.md): A node state in Netdata Cloud indicating the node is disconnected and no data is available. Also referred to as "Unreachable" in code. See [Node States and Transitions](/docs/netdata-cloud/node-states-and-transitions.md).
108 +
109 - [**Obsoletion**(of nodes)](/docs/dashboards-and-charts/nodes-tab.md): Removing nodes from a space.
110
111 - [**Orchestrators**](/src/collectors/README.md): External plugins that run and manage one or more modules. They run as independent processes.
@@ -118,6 +126,8 @@ Missing a term? Let us know or submit a request to expand our glossary. Together
126
127 - [**Single Node Dashboard**](/docs/dashboards-and-charts/metrics-tab-and-single-node-tabs.md): A dashboard pre-configured with every installation of the Netdata Agent, with thousands of metrics and hundreds of interactive charts that requires no setup.
128
129 +- [**Stale** (node state)](/docs/netdata-cloud/node-states-and-transitions.md): A node state in Netdata Cloud indicating a child node stopped streaming to its Parent, but the Parent is still online and has historical data available. See [Node States and Transitions](/docs/netdata-cloud/node-states-and-transitions.md).
130 +
131 - [**Space**](/docs/netdata-cloud/organize-your-infrastructure-invite-your-team.md#overview): A high-level container and virtual collaboration area where you can organize team members, access levels, and the nodes you want to monitor.
132
133 ## T
@@ -131,6 +141,8 @@ Missing a term? Let us know or submit a request to expand our glossary. Together
141 - [**Unlimited Scalability**](https://www.netdata.cloud/#:~:text=love%20community%20contributions!-,Infinite%20Scalability,-By%20storing%20data): With Netdata's distributed architecture, you can seamlessly observe a couple, hundreds or
142 even thousands of nodes. There are no actual bottlenecks especially if you retain metrics locally in the Agents.
143
144 +- [**Unseen** (node state)](/docs/netdata-cloud/node-states-and-transitions.md): A node state in Netdata Cloud indicating the node was claimed but has never connected. Also referred to as "Created" in code. See [Node States and Transitions](/docs/netdata-cloud/node-states-and-transitions.md).
145 +
146 ## V
147
148 - [**Visualizations**](/docs/dashboards-and-charts/README.md): Netdata uses dimensions, contexts, and families to sort your metric data into graphs, charts, and alerts that maximize your understanding of your infrastructure and your ability to troubleshoot it, along or on a team.
docs/learn/remove-node.md
+6 -2
@@ -6,9 +6,11 @@ You can remove a node from your Space in Netdata Cloud, but the process depends
6
7 Before attempting to remove a node, it's important to understand what each status means:
8
9 -* **Online**: Node is actively connected and streaming data
9 +* **Online** (Live): Node is actively connected and streaming data
10 * **Stale**: Node is a child that stopped streaming to its parent, but the parent still has its historical data
11 -* **Offline**: Node is disconnected and no longer has data available for querying
11 +* **Offline** (Unreachable): Node is disconnected and no longer has data available for querying
12 +
13 +For a complete explanation of node states, state transitions, and when nodes move between states, see [Node States and Transitions](/docs/netdata-cloud/node-states-and-transitions.md).
14
15 <details>
16 <summary><strong>Why Can't I Delete Stale Nodes?</strong></summary><br/>
@@ -136,6 +138,8 @@ To prevent removed nodes from reappearing:
138
139 ## Additional Resources
140
141 +For a complete reference on node states and transitions, see [Node States and Transitions](/docs/netdata-cloud/node-states-and-transitions.md).
142 +
143 For more advanced configuration options with streaming setups, see [Nodes Ephemerality](/docs/nodes-ephemerality.md).
144
145 To avoid removal issues when cloning VMs, see [VM Templates](/docs/learn/vm-templates.md) for proper identity cleanup.
docs/netdata-cloud/node-states-and-transitions.md new
+282
@@ -0,0 +1,282 @@
1 +# Node States
2 +
3 +Netdata provides dashboards at multiple levels of your infrastructure. Each level displays node states based on what it can observe. This page explains what each state means, when transitions happen, and how to configure the behavior.
4 +
5 +## Dashboard Levels
6 +
7 +Netdata's distributed architecture provides three observation points:
8 +
9 +| Dashboard | What You See | How to Access |
10 +|-----------|--------------|---------------|
11 +| **Agent** | Local node only | `http://node-ip:19999` |
12 +| **Parent** | All nodes streaming to this Parent | `http://parent-ip:19999` |
13 +| **Netdata Cloud** | All nodes claimed to your Space | `https://app.netdata.cloud` |
14 +
15 +**How data flows:**
16 +
17 +```
18 +Agent → (streaming) → Parent → (ACLK) → Netdata Cloud
19 +Agent → (ACLK) → Netdata Cloud (standalone, no Parent)
20 +```
21 +
22 +Node states reflect this flow: if a link breaks, states change based on where data is still available.
23 +
24 +## States on Netdata Cloud
25 +
26 +| State | Meaning |
27 +|-------|---------|
28 +| **Live** | Node is connected to Netdata Cloud (directly or via Parents) and providing live metrics |
29 +| **Stale** | Node disconnected, but a Parent connected to Netdata Cloud has its historical data |
30 +| **Offline** | Node is disconnected and no data is available |
31 +| **Unseen** | Node was claimed but has never connected |
32 +
33 +### Stale vs Offline
34 +
35 +The difference is **data availability**:
36 +
37 +| Scenario | State | Can Query Data? |
38 +|----------|-------|-----------------|
39 +| Child disconnected, Parent connected to Cloud | **Stale** | Yes, via Parent |
40 +| Standalone Agent disconnected | **Offline** | No |
41 +| Child disconnected, all Parents disconnected from Cloud | **Offline** | No |
42 +
43 +Stale nodes remain queryable because the Parent serves as a data cache. This is why you cannot delete Stale nodes from the UI—they still have accessible data.
44 +
45 +## States on Parent Dashboards
46 +
47 +Parents display nodes that stream (or have streamed) to them:
48 +
49 +| State | Meaning |
50 +|-------|---------|
51 +| **Live** | Node is actively streaming metrics |
52 +| **Stale** | Node stopped streaming, historical data retained |
53 +
54 +Parents don't show Offline or Unseen states. When a node's retention expires or cleanup runs, it disappears from the Parent's view entirely.
55 +
56 +## State Mapping: Parent → Cloud
57 +
58 +When a Parent connects to Netdata Cloud, it reports the state of all its children:
59 +
60 +| Parent Sees | Cloud Shows | Why |
61 +|-------------|-------------|-----|
62 +| Live | **Live** | Data flowing through Parent |
63 +| Stale | **Stale** | Parent connected to Cloud has historical data |
64 +| (removed) | **Offline** | No data source available |
65 +
66 +**High-availability setups (recommended):**
67 +With two Parents (Child → P1 → P2), children stream to one Parent, which replicates to the other. Both Parents connect to Cloud.
68 +
69 +If the child connects to Cloud only via Parents:
70 +
71 +| Event | Result | Why |
72 +|-------|--------|-----|
73 +| P1 disconnects from Cloud | No change (Live) | P1 still runs, replicates to P2, P2 reports to Cloud |
74 +| P1 stops | Brief Stale, then Live | Child fails over to P2 |
75 +| P2 disconnects from Cloud | No change (Live) | P1 still connected to Cloud |
76 +| P2 stops | No change (Live) | Child still streams to P1, P1 reports to Cloud |
77 +| Both disconnect from Cloud | **Offline** | No Parent can report to Cloud |
78 +
79 +If the child also connects directly to Cloud, it remains Live regardless of Parent status.
80 +
81 +**Single Parent setups:**
82 +When the only Parent disconnects from Cloud, all its children become **Offline** because Cloud can no longer query their data.
83 +
84 +**When a Parent reconnects:**
85 +Children with retained data appear as **Stale** (or **Live** if actively streaming).
86 +
87 +## Transition Timings
88 +
89 +### Detection Speed
90 +
91 +**Netdata Cloud detects agent/parent disconnection:**
92 +
93 +| Event | Detection Time | Mechanism |
94 +|-------|----------------|-----------|
95 +| Agent or Parent loses Cloud connection | **~60 seconds** | MQTT keepalive (60s interval) |
96 +| UI reflects state change | **1-2 minutes** | Cloud processing + UI refresh |
97 +
98 +**Parent detects child disconnection:**
99 +
100 +| Event | Detection Time | Mechanism |
101 +|-------|----------------|-----------|
102 +| Child shuts down gracefully | **Immediate** | Socket close detected |
103 +| Child crashes or network drops | **~60 seconds** | TCP keepalive probes (30s idle + 3×10s probes) |
104 +| Child silently stops sending data | **10 minutes** | Idle activity timeout |
105 +
106 +These timings are hardcoded and not user-configurable.
107 +
108 +### Standalone Agent Transitions
109 +
110 +A standalone Agent connects directly to Cloud without a Parent.
111 +
112 +| Event | From | To | Timing |
113 +|-------|------|-----|--------|
114 +| Agent starts, connects to Cloud | Unseen/Offline | **Live** | Immediate on connection |
115 +| Agent stops or loses network | Live | **Offline** | Immediate to ~60 seconds |
116 +| Agent restarts | Offline | **Live** | Immediate on reconnection |
117 +
118 +**No Stale state**: Standalone agents go directly to Offline because there's no Parent holding their data.
119 +
120 +### Child Node Transitions
121 +
122 +A child streams metrics to a Parent, which connects to Cloud.
123 +
124 +| Event | From | To | Timing |
125 +|-------|------|-----|--------|
126 +| Child connects to Parent | Unseen/Offline | **Live** | Immediate |
127 +| Child stops streaming | Live | **Stale** | Immediate to ~60 seconds (see Detection Speed) |
128 +| Child restarts streaming | Stale | **Live** | Immediate |
129 +| All Parents go offline | Live/Stale | **Offline** | Immediate to ~60 seconds |
130 +| Parent reconnects (child still down) | Offline | **Stale** | Immediate (if data retained) |
131 +
132 +### First Connection
133 +
134 +| Event | From | To | Timing |
135 +|-------|------|-----|--------|
136 +| Node claimed to Space | - | **Unseen** | Immediate |
137 +| Node connects for first time | Unseen | **Live** | Immediate on connection |
138 +
139 +## Automatic Cleanup
140 +
141 +### Netdata Cloud Cleanup
142 +
143 +Cloud automatically removes nodes that remain Offline or Unseen:
144 +
145 +| Node Type | Cleanup After | Notes |
146 +|-----------|---------------|-------|
147 +| Standalone agents (0 hops) | **7 days** | Direct Cloud connection |
148 +| Child nodes (1+ hops) | **48 hours** | Connected via Parent |
149 +| Unseen nodes | **48 hours** | Claimed but never connected |
150 +
151 +**Stale nodes are never automatically removed.** They have queryable data via their Parent.
152 +
153 +These thresholds are managed by Netdata Cloud infrastructure and are not user-configurable.
154 +
155 +## Configuration Options
156 +
157 +### Ephemeral Nodes
158 +
159 +For dynamic infrastructure (auto-scaling groups, containers, spot instances), mark nodes as ephemeral:
160 +
161 +```ini
162 +# On the child node's netdata.conf
163 +[global]
164 + is ephemeral node = yes
165 +```
166 +
167 +**Effects:**
168 +- No disconnection alerts for this node
169 +- Node label `_is_ephemeral=true` propagates to Parents and Cloud
170 +
171 +### Marking Existing Nodes as Ephemeral
172 +
173 +To mark already-offline nodes as ephemeral (clears alerts, keeps data queryable):
174 +
175 +```bash
176 +netdatacli mark-stale-nodes-ephemeral <node-id | hostname | ALL_NODES>
177 +```
178 +
179 +### Removing Nodes
180 +
181 +To force-remove a Stale node:
182 +
183 +```bash
184 +netdatacli remove-stale-node <node-id | hostname | ALL_NODES>
185 +```
186 +
187 +This sends an offline signal to Cloud. The node transitions to Offline and becomes eligible for cleanup (or immediate UI deletion).
188 +
189 +See [Remove Node](/docs/learn/remove-node.md) for detailed instructions.
190 +
191 +### Connection Hops
192 +
193 +Check how a node connects to Cloud:
194 +
195 +| Hops | Meaning |
196 +|------|---------|
197 +| 0 | Direct Cloud connection (standalone) |
198 +| 1 | Connected via one Parent |
199 +| 2+ | Connected via chained Parents |
200 +
201 +View hops in Netdata Cloud by clicking the node info button.
202 +
203 +Nodes with more hops have more potential failure points, but also benefit from Parent data caching (Stale state instead of Offline).
204 +
205 +## Troubleshooting
206 +
207 +### Log Filtering with MESSAGE_ID
208 +
209 +Netdata logs include MESSAGE_IDs for filtering specific events. Use `journalctl` to view relevant logs:
210 +
211 +```bash
212 +# Cloud connection events (ACLK)
213 +journalctl -u netdata MESSAGE_ID=acb33cb9-5778-476b-aac7-02eb7e4e151d
214 +
215 +# Streaming from children (on Parent)
216 +journalctl -u netdata MESSAGE_ID=ed4cdb8f-1beb-4ad3-b57c-b3cae2d162fa
217 +
218 +# Streaming to parent (on Child)
219 +journalctl -u netdata MESSAGE_ID=6e2e3839-0676-4896-8b64-6045dbf28d66
220 +```
221 +
222 +### Node shows Stale, expected Live
223 +
224 +**Cause:** Node stopped streaming to its Parent.
225 +
226 +**Check:**
227 +1. Is the node's Netdata Agent running? `systemctl status netdata`
228 +2. Can the node reach the Parent? Check network/firewall
229 +3. Check streaming config: `cat /etc/netdata/stream.conf`
230 +4. Check agent logs: `journalctl -u netdata | grep -i stream`
231 +
232 +### Node shows Offline, expected Stale
233 +
234 +**Cause:** Either it's a standalone Agent, or all its Parents are disconnected from Cloud.
235 +
236 +**Check:**
237 +1. Is this a standalone Agent or does it stream to a Parent?
238 +2. If streaming: Is the Parent online and connected to Cloud?
239 +3. Check Parent's dashboard—does it show the child?
240 +
241 +### Node shows Unseen
242 +
243 +**Cause:** Node was claimed but never successfully connected to Cloud.
244 +
245 +**Check:**
246 +1. Is the Netdata Agent running?
247 +2. Can the agent reach `app.netdata.cloud`? Check firewall/proxy
248 +3. Is the claiming token correct?
249 +4. Check agent logs: `journalctl -u netdata | grep -i aclk`
250 +
251 +### All children went Offline simultaneously
252 +
253 +**Cause:** All Parents lost their Cloud connection. With HA setups (two Parents), this only happens if both disconnect.
254 +
255 +**Check:**
256 +1. Are the Parents online? `systemctl status netdata`
257 +2. Can they reach Cloud? Check network
258 +3. Check Parent logs: `journalctl -u netdata | grep -i aclk`
259 +
260 +### Can't delete node from UI
261 +
262 +**Cause:** Node is Stale (has data via Parent). UI prevents deletion to protect queryable data.
263 +
264 +**Solution:** Use CLI to remove:
265 +```bash
266 +netdatacli remove-stale-node <node-id>
267 +```
268 +
269 +### Node reappears after deletion
270 +
271 +**Cause:** Agent is still running and configured to reconnect.
272 +
273 +**Solution:**
274 +1. Stop the agent: `systemctl stop netdata`
275 +2. Remove claim: `rm /var/lib/netdata/cloud.d/claimed_id`
276 +3. Clear environment variables if set
277 +
278 +## See Also
279 +
280 +- [Node Types and Lifecycle](/docs/nodes-ephemerality.md) - Ephemeral vs permanent nodes
281 +- [Remove Node](/docs/learn/remove-node.md) - Detailed removal instructions
282 +- [Streaming Configuration](/docs/observability-centralization-points/metrics-centralization-points/README.md) - Parent-child setup
docs/nodes-ephemerality.md
+9 -1
@@ -53,8 +53,15 @@ Netdata Cloud automatically removes inactive nodes to keep your dashboards clean
53 | Node Type | Offline Duration | Description |
54 |------------------------------|------------------|------------------------------------------------------------------------------------------------------------------------------------|
55 | **Child nodes** | 48 hours | Nodes that connect through a Parent node. Deleted when:<br />• The child node goes offline, OR<br />• The Parent node goes offline |
56 -| **Directly connected nodes** | 60 days | Nodes claimed directly to Netdata Cloud without going through a Parent. |
56 +| **Directly connected nodes** | 7 days | Nodes claimed directly to Netdata Cloud without going through a Parent. |
57 | **Ephemeral nodes** | Custom | Temporary nodes (containers, auto-scaling VMs) with configurable cleanup periods. See configuration below. |
58 +| **Unseen nodes** | 48 hours | Nodes that were claimed but have never connected to Netdata Cloud. |
59 +
60 +:::tip
61 +
62 +**Stale nodes are NOT automatically deleted.** Only Offline and Unseen nodes are subject to automatic cleanup. A Stale node has historical data available via a Parent, so it's preserved until the Parent goes offline or the data expires.
63 +
64 +:::
65
66 :::info Important
67
@@ -163,5 +170,6 @@ flowchart TD
170
171 ## See Also
172
173 +- [Node States and Transitions](/docs/netdata-cloud/node-states-and-transitions.md) - Comprehensive reference for node states (Live, Stale, Offline, Unseen) and transition triggers
174 - [Node Identities](/docs/learn/node-identities.md) - Understand how node identity works alongside ephemerality
175 - [VM Templates](/docs/learn/vm-templates.md) - Configure ephemerality in VM templates for auto-scaling groups
docs/observability-centralization-points/metrics-centralization-points/README.md
+2
@@ -92,3 +92,5 @@ Copies **recent past samples** (replication) and **real-time new samples** (stre
92 ## **Best Practices**
93
94 For detailed guidelines, check [Best Practices for Observability Centralization Points](/docs/observability-centralization-points/best-practices.md).
95 +
96 +To understand how node connection states (Live, Stale, Offline) work with Parent-Child setups, see [Node States and Transitions](/docs/netdata-cloud/node-states-and-transitions.md).