diff options
| author | Kamil Kieliszczyk <kamil@kieliszczyk.net> | 2023-07-28 11:26:35 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-07-28 12:26:35 +0300 |
| commit | ea23a946ec377ec64ed4e7877d41a94f2613f1d6 (patch) | |
| tree | 6778a05e4322678efd718ed924034c311659bf10 /docs/category-overview-pages | |
| parent | 8274d44f1f7c61672ef1a3dc90708f54063c3ff0 (diff) | |
Update documentation (#15606)
Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
Diffstat (limited to 'docs/category-overview-pages')
| -rw-r--r-- | docs/category-overview-pages/deployment-strategies.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/category-overview-pages/deployment-strategies.md b/docs/category-overview-pages/deployment-strategies.md index b07fc0d172..f8a68b46ff 100644 --- a/docs/category-overview-pages/deployment-strategies.md +++ b/docs/category-overview-pages/deployment-strategies.md @@ -49,7 +49,7 @@ An Agent connected to a Parent is called a _Child_. It will _stream_ metrics to When using Cloud, it is recommended that just the Parent is connected to Cloud. Child Agents can then be configured to have short retention, in RAM instead of on Disk, and have alerting and other features disabled. Because they don't need to connect to Cloud themselves, those children can then be further secured by not allowing outbound traffic. - + This setup allows for leaner Child nodes and is good for setups with more than a handful of nodes. Metrics data remains accessible if the Child node is temporarily unavailable or decommissioned, although there is no failover in case the Parent becomes unavailable. @@ -60,7 +60,7 @@ For high availability, Parents can be configured to stream data for their childr With both Parent Agents connected to Cloud, Cloud will route queries to either Parent transparently, depending on their availability. Alerts trigger on either Parent will stream to Cloud, and Cloud will deduplicate and debounce state changes to prevent spurious notifications. - + ## Configuration Details |