Skip to content

README.md

Latest commit

 

History

History
110 lines (75 loc) · 4.78 KB

README.md

File metadata and controls

110 lines (75 loc) · 4.78 KB

Configure Netdata Parents to centralize metrics

How Metrics Centralization Works

flowchart BT
    C1("**Netdata Child 1**<br/><br/>Production System")
    C2("**Netdata Child 2**<br/><br/>Production System")
    C3("**Netdata Child N**<br/><br/>Production System")
    P1("**Netdata Parent 1**<br/><br/>Centralization Point")
    C1 -->|stream| P1
    C2 -->|stream| P1
    C3 -->|stream| P1
    
    %% Style definitions
    classDef child fill:#ffeb3b,stroke:#000000,stroke-width:3px,color:#000000,font-size:16px
    classDef parent fill:#4caf50,stroke:#000000,stroke-width:3px,color:#000000,font-size:16px
    
    %% Apply styles
    class C1,C2,C3 child
    class P1 parent
Loading

Installation

A Netdata Parent is a regular Netdata Agent configured to receive streaming metrics from Netdata Children (also normal Agents!).

To install a Netdata Parent:

  1. Install Netdata on your Parent node.

    For installation instructions, see the Installation section.

  2. After installation, configure stream.conf to enable reception from Children.

    See Configuring Metrics Centralization Points for detailed configuration instructions.

Key Features

:::important

Netdata Streaming and Replication

Copies recent past samples (replication) and real-time new samples (streaming) from production systems (Netdata Children) to metrics centralization points (Netdata Parents). Netdata Parents store the database for these metrics based on retention settings.

:::

How Your Systems Connect

Netdata Child Behavior
  • Each Netdata Child can stream to only one Netdata Parent at a time.
  • Multiple Netdata Parents can be configured for high availability, but only the first working one will be used.

Netdata Parent Capabilities
  • Receives metric samples from multiple Netdata Children.
  • Can re-stream received metrics to another Netdata Parent, forming an infinite hierarchy of Parents.
  • Supports Netdata Parents Clusters for high availability.

Feature Comparison

Feature Netdata Child (Production System) Netdata Parent (Centralization Point)
Metrics Retention Minimal retention; can use ram or alloc mode. Stores metrics for all connected systems.
Machine Learning Can be disabled (default: enabled). Runs anomaly detection for all connected systems.
Alerts & Notifications Can be disabled (default: enabled). Monitors health and sends alerts for all systems.
API & Dashboard Can be disabled (default: enabled). Hosts the dashboard using its own retention settings.
Exporting Metrics Optional (default: enabled). Exports all collected metrics.
Netdata Functions Child must be online to function. Forwards function requests to connected Children.
Netdata Cloud Not required. Registers all connected systems to Netdata Cloud.

Supported Configurations

For Netdata Children

  • Full Mode (Default):
    • All Netdata features are enabled (machine learning, alerts, notifications, dashboard, etc.).
  • Thin Mode:
    • Only collects and forwards metrics to a Parent.
    • Some local retention is kept to handle network issues, but all other features are disabled.

For Netdata Parents

  • Standalone:
    • A single Parent in the infrastructure or the top-most Parent in a hierarchy.
  • Cluster:
    • A group of Parents that share the same data from the same Children.
    • Provides high availability.
  • Proxy:
    • Stores received metrics locally and forwards them to a higher-level Parent (Grand Parent).

Cluster Configuration

  • A Cluster consists of circular Proxy nodes, where each Parent acts as a Parent to the others.
  • Only the top level of a multi-level hierarchy can be configured as a cluster.

Best Practices

For detailed guidelines, check Best Practices for Observability Centralization Points.

To understand how node connection states (Live, Stale, Offline) work with Parent-Child setups, see Node States and Transitions.