mirror of
https://github.com/netdata/netdata.git
synced 2025-04-29 15:10:02 +00:00
86eb74af33
* Observability cent points improved * Observability cent points 2 * fix formatting * fixes --------- Co-authored-by: ilyam8 <ilya@netdata.cloud> |
||
|---|---|---|
| .. | ||
| logs-centralization-points-with-systemd-journald | ||
| metrics-centralization-points | ||
| best-practices.md | ||
| README.md | ||
Observability Centralization Points
Netdata allows you to set up multiple Observability Centralization Points to aggregate metrics, logs, and metadata across your infrastructure.
Why Use Centralization Points?
-
Ephemeral Systems:
- Ideal for Kubernetes nodes or temporary VMs that frequently go offline.
- Ensures metrics and logs remain available for analysis and troubleshooting.
-
Limited Resources:
- Offloads observability tasks from systems with low disk space, CPU, RAM, or I/O bandwidth.
- Keeps production systems running efficiently without performance trade-offs.
-
Multi-Node Dashboards Without Netdata Cloud:
- Aggregates data from multiple nodes for centralized dashboards, similar to Netdata Cloud.
-
Restricted Netdata Cloud Access:
- Acts as a bridge when monitored systems can’t connect to Netdata Cloud due to firewall restrictions.
How Multiple Centralization Points Work
- With Netdata Cloud:
- Queries all centralization points in parallel for a unified view of the infrastructure.
- Without Netdata Cloud:
- Parent nodes consolidate data from connected systems, providing a local view of metrics and logs.