archive/netdata_netdata
0
0
Fork 0
mirror of https://github.com/netdata/netdata.git synced 2025-04-06 06:25:32 +00:00
Code Issues Projects Releases Wiki Activity
netdata_netdata/docs/observability-centralization-points
History
Fotis Voutsas f27f4f714a
Documentation changes, new files and restructuring the hierarchy () 
* docs additions

* docs from writerside, not to be published in this state, links need work and Learn map needs to include them

* rename some files to reduce repetition on filenames

* use new packaging documentation and replace links to old

* change learn-rel-path to new category names

* replace configuration file with new one, add conf directory section to it, and replace links to point to that

* linkfix

* run integrations pipeline to get new links

* catoverpage

* fix writerside style links

* addition in on-prem mention

* comment out mermaid problematic line

* change path of alerting integrations docs for Learn

* fix

* fixes

* fix diagrams
2024-02-20 09:08:46 +02:00
..
logs-centralization-points-with-systemd-journald Documentation changes, new files and restructuring the hierarchy () 2024-02-20 09:08:46 +02:00
metrics-centralization-points Documentation changes, new files and restructuring the hierarchy () 2024-02-20 09:08:46 +02:00
best-practices.md Documentation changes, new files and restructuring the hierarchy () 2024-02-20 09:08:46 +02:00
README.md Documentation changes, new files and restructuring the hierarchy () 2024-02-20 09:08:46 +02:00

README.md

Observability Centralization Points

Netdata supports the creation of multiple independent Observability Centralization Points, aggregating metric samples, logs and metadata within an infrastructure.

Observability Centralization Points are crucial for ensuring comprehensive monitoring and observability across an infrastructure, particularly under the following conditions:

  1. Ephemeral Systems: For systems like Kubernetes nodes or ephemeral VMs that may not be persistently available, centralization points ensure that metrics and logs are not lost when these systems go offline. This is essential for maintaining historical data for analysis and troubleshooting.

  2. Resource Constraints: In scenarios where the monitored systems lack sufficient resources (disk space or I/O bandwidth, CPU, RAM) to handle observability tasks effectively, centralization points offload these responsibilities, ensuring that production systems can operate efficiently without compromise.

  3. Multi-node Dashboards without Netdata Cloud: For environments requiring aggregated views across multiple nodes but without the use of Netdata Cloud, Netdata Parents can aggregate this data to provide comprehensive dashboards, similar to what Netdata Cloud offers.

  4. Netdata Cloud Access Restrictions: In cases where monitored systems cannot connect to Netdata Cloud (due to a firewall policy), a Netdata Parent can serve as a bridge, aggregating data and interfacing with Netdata Cloud on behalf of these restricted systems.

When multiple independent centralization points are available:

  • Netdata Cloud queries all of them in parallel, to provide a unified infrastructure view.

  • Without Netdata Cloud, the dashboards of each of the Netdata Parents provide unified views of the infrastructure aggregated to each of them (metrics and logs).