diff --git a/docs/Exporting Metrics/Enable an exporting connector.mdx b/docs/Exporting Metrics/Enable an exporting connector.mdx index 49bb445cef..a7c0d7e086 100644 --- a/docs/Exporting Metrics/Enable an exporting connector.mdx +++ b/docs/Exporting Metrics/Enable an exporting connector.mdx @@ -71,3 +71,29 @@ Replace `netdata` with an instance name of your choice, and change the `destinat Any further configuration is optional, based on your needs and the configuration of your Graphite database. See the [Graphite connector doc](/docs/exporting-metrics/connectors/graphite) and [exporting engine reference](/docs/exporting-metrics/exporting-reference#configuration-structure) for details. + +
+Export to Multiple Databases Simultaneously + +You can export metrics to more than one external database at the same time. To do this, add a separate connector section for each destination in the same `exporting.conf` file. Every section that has `enabled = yes` exports independently to its own destination, so by default all enabled destinations receive the same metrics from your Agent, unless you configure different settings per section, as described below. + +For example, to export to both a Graphite database and an OpenTSDB HTTP database, combine the two connector sections in a single `exporting.conf`: + +```text +[exporting:global] + enabled = yes + +[graphite:my_graphite_instance] + enabled = yes + destination = localhost:2003 + +[opentsdb:http:my_opentsdb_http_instance] + enabled = yes + destination = localhost:4242 +``` + +Replace the instance names and `destination` values with those of your own databases. [Restart your Agent](/docs/netdata-agent/maintenance/service-control) to start exporting. As with a single connector, all enabled destinations begin receiving metrics **starting from the Agent restart time**, not the historical database. + +You can add as many connector sections as you need, even mixing different connector types in the same file. Each section can also define its own settings, such as its own `destination`, export interval, and metric filters. See the [exporting engine reference](/docs/exporting-metrics/exporting-reference#configuration-structure) for the full set of per-section options. + +
diff --git a/docs/Netdata Agent/Configuration/Daemon.mdx b/docs/Netdata Agent/Configuration/Daemon.mdx index 9ef9ba38c7..5926dfa702 100644 --- a/docs/Netdata Agent/Configuration/Daemon.mdx +++ b/docs/Netdata Agent/Configuration/Daemon.mdx @@ -59,12 +59,14 @@ After you modify `netdata.conf`, you need to [restart Netdata](/docs/netdata-age To override the auto-detected hostname and control how your node appears in Dashboards, Netdata Cloud, alert notifications, and streaming Parent nodes: 1. Edit your `netdata.conf` file: + ```bash cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata sudo ./edit-config netdata.conf ``` 2. Add or modify the `hostname` in the `[global]` section: + ```ini [global] hostname = YOUR_CUSTOM_NODE_NAME @@ -89,7 +91,7 @@ To override the auto-detected hostname and control how your node appears in Dash | timezone | auto-detected | The timezone retrieved from the environment variable | | run as user | `netdata` | The user Netdata will run as. | | pthread stack size | auto-detected | | -| crash reports | `all` or `off` | `all` when anonymous telemetry is enabled, or the agent is claimed or connected to Netdata Cloud (directly or via a Netdata Parent). When it is `all` Netdata reports restarts and crashes. It can also be `crashes` to report only crashes. When it is `off` nothing is reported. Each kind of event is deduplicated and reported at most once per day. [Read more at this blog post](https://www.netdata.cloud/blog/2025-03-06-monitoring-netdata-restarts/). | +| crash reports | `all` or `off` | `all` when anonymous telemetry is enabled, or the agent is claimed or connected to Netdata Cloud (directly or via a Netdata Parent). When it is `all` Netdata reports restarts and crashes. It can also be `crashes` to report only crashes. When it is `off` nothing is reported. Each kind of event is deduplicated and reported at most once per day. [Read more at this blog post](https://www.netdata.cloud/blog/2025-03-06-monitoring-netdata-restarts/). | **Profiles**: @@ -118,22 +120,22 @@ A few of these settings can be individually configured in `netdata.conf`, like t
Database Section Options -| setting | default | info | -|:---------------------------------------------:|:------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| mode | `dbengine` | `dbengine`: The default for long-term metrics storage with efficient RAM and disk usage. Can be extended with `dbengine page cache size` and `dbengine tier X retention size`.
`ram`: The round-robin database will be temporary and it will be lost when Netdata exits.
`alloc`: Similar to `ram`, but can significantly reduce memory usage, when combined with a low retention and does not support KSM.
`none`: Disables the database at this host, and disables Health monitoring entirely, as that requires a database of metrics. Not to be used together with streaming. | -| retention | `3600` | Used with `mode = ram/alloc`, not the default `mode = dbengine`. This number reflects the number of entries the `netdata` daemon will by default keep in memory for each chart dimension. Check [Memory Requirements](/docs/netdata-agent/resource-utilization/disk-&-retention) for more information. | -| storage tiers | `3` | The number of storage tiers you want to have in your dbengine. Check the tiering mechanism in the [dbengine's reference](/docs/developer-and-contributor-corner/database-engine#tiers). You can have up to 5 tiers of data (including the _Tier 0_). This number ranges between 1 and 5. | -| dbengine page cache size | `32MiB` | Determines the amount of RAM in MiB that is dedicated to caching for _Tier 0_ Netdata metric values. | -| dbengine tier **`N`** retention size | `1GiB` | The disk space dedicated to metrics storage, per tier. Can be used in single-node environments as well.
`N belongs to [1..4]` | -| dbengine tier **`N`** retention time | `14d`, `3mo`, `1y`, `1y`, `1y` | The database retention, expressed in time. Can be used in single-node environments as well.
`N belongs to [1..4]` | -| update every | `1` | The frequency in seconds, for data collection. For more information see the [performance guide](/docs/netdata-agent/configuration/performance-optimization). These metrics stored as _Tier 0_ data. Explore the tiering mechanism in the [dbengine's reference](/docs/developer-and-contributor-corner/database-engine#tiers). | -| dbengine tier **`N`** update every iterations | `60` | The down sampling value of each tier from the previous one. For each Tier, the greater by one Tier has N (equal to 60 by default) less data points of any metric it collects. This setting can take values from `2` up to `255`.
`N belongs to [1..4]` | -| dbengine tier back fill | `new` | Specifies the strategy of recreating missing data on higher database Tiers.
`new`: Sees the latest point on each Tier and save new points to it only if the exact lower Tier has available points for it's observation window (`dbengine tier N update every iterations` window).
`none`: No back filling is applied.
`N belongs to [1..4]` | -| memory deduplication (ksm) | `yes` | When set to `yes`, Netdata will offer its in-memory round robin database and the dbengine page cache to kernel same page merging (KSM) for deduplication. | -| cleanup obsolete charts after | `1h` | See [monitoring ephemeral containers](/docs/collecting-metrics/containers-and-cgroups#monitoring-ephemeral-containers), also sets the timeout for cleaning up obsolete dimensions | -| gap when lost iterations above | `1` | | -| cleanup orphan hosts after | `1h` | How long to wait until automatically removing from the DB a remote Netdata host (child) that is no longer sending data. | -| enable zero metrics | `no` | Set to `yes` to show charts when all their metrics are zero. | +| setting | default | info | +|:---------------------------------------------:|:------------------------------:|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| db | `dbengine` | `dbengine`: The default for long-term metrics storage with efficient RAM and disk usage. Can be extended with `dbengine page cache size` and `dbengine tier X retention size`.
`ram`: The round-robin database will be temporary and it will be lost when Netdata exits.
`alloc`: Similar to `ram`, but can significantly reduce memory usage, when combined with a low retention and does not support KSM.
`none`: Disables the database at this host, and disables Health monitoring entirely, as that requires a database of metrics. Not to be used together with streaming. `mode` is also accepted for backwards compatibility. | +| retention | `3600` | Used with `db = ram/alloc`, not the default `db = dbengine`. This number reflects the number of entries the `netdata` daemon will by default keep in memory for each chart dimension. Check [Memory Requirements](/docs/netdata-agent/resource-utilization/disk-&-retention) for more information. | +| storage tiers | `3` | The number of storage tiers you want to have in your dbengine. Check the tiering mechanism in the [dbengine's reference](/docs/developer-and-contributor-corner/database-engine#tiers). You can have up to 5 tiers of data (including the _Tier 0_). This number ranges between 1 and 5. | +| dbengine page cache size | `32MiB` | Determines the amount of RAM in MiB that is dedicated to caching for _Tier 0_ Netdata metric values. | +| dbengine tier **`N`** retention size | `1GiB` | The disk space dedicated to metrics storage, per tier. Can be used in single-node environments as well.
`N belongs to [1..4]` | +| dbengine tier **`N`** retention time | `14d`, `3mo`, `1y`, `1y`, `1y` | The database retention, expressed in time. Can be used in single-node environments as well.
`N belongs to [1..4]` | +| update every | `1` | The frequency in seconds, for data collection. For more information see the [performance guide](/docs/netdata-agent/configuration/performance-optimization). These metrics stored as _Tier 0_ data. Explore the tiering mechanism in the [dbengine's reference](/docs/developer-and-contributor-corner/database-engine#tiers). | +| dbengine tier **`N`** update every iterations | `60` | The down sampling value of each tier from the previous one. For each Tier, the greater by one Tier has N (equal to 60 by default) less data points of any metric it collects. This setting can take values from `2` up to `255`.
`N belongs to [1..4]` | +| dbengine tier back fill | `new` | Specifies the strategy of recreating missing data on higher database Tiers.
`new`: Sees the latest point on each Tier and save new points to it only if the exact lower Tier has available points for it's observation window (`dbengine tier N update every iterations` window).
`none`: No back filling is applied.
`N belongs to [1..4]` | +| memory deduplication (ksm) | `yes` | When set to `yes`, Netdata will offer its in-memory round robin database and the dbengine page cache to kernel same page merging (KSM) for deduplication. | +| cleanup obsolete charts after | `1h` | See [monitoring ephemeral containers](/docs/collecting-metrics/containers-and-cgroups#monitoring-ephemeral-containers), also sets the timeout for cleaning up obsolete dimensions | +| gap when lost iterations above | `1` | | +| cleanup orphan hosts after | `1h` | How long to wait until automatically removing from the DB a remote Netdata host (child) that is no longer sending data. | +| enable zero metrics | `no` | Set to `yes` to show charts when all their metrics are zero. | :::info Storage Tiers The multiplication of all the **enabled** tiers `dbengine tier N update every iterations` values must be less than `65535`. @@ -148,7 +150,7 @@ The multiplication of all the **enabled** tiers `dbengine tier N update every it |:-------------------:|:------------------------------------------------------------------:|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | config | `/etc/netdata` | The directory configuration files are kept. | | stock config | `/usr/lib/netdata/conf.d` | | -| stock data | `/usr/share/netdata` | The directory Netdata uses for immutable stock data files shipped with the installation. | +| stock data | `/usr/share/netdata` | The directory Netdata uses for immutable stock data files shipped with the installation. | | log | `/var/log/netdata` | The directory in which the [log files](/docs/netdata-agent/daemon#logging) are kept. | | web | `/usr/share/netdata/web` | The directory the web static files are kept. | | cache | `/var/cache/netdata` | The directory the memory database will be stored if and when Netdata exits. Netdata will re-read the database when it will start again, to continue from the same point. | @@ -223,7 +225,7 @@ Specific Alerts are configured in per-collector config files under the `health.d | in memory max Health log entries | 1000 | Size of the Alert history held in RAM | | script to execute on alarm | `/usr/libexec/netdata/plugins.d/alarm-notify.sh` | The script that sends Alert notifications. Note that in versions before 1.16, the plugins.d directory may be installed in a different location in certain OSs (e.g. under `/usr/lib/netdata`). | | run at least every | `10s` | Controls how often all Alert conditions should be evaluated. | -| notification execution timeout | `2m` | How long a notification command (e.g. `alarm-notify.sh`) may run before it is killed. Protects Alert evaluation from hung notification processes. Set to `0` to wait forever. | +| notification execution timeout | `2m` | How long a notification command (e.g. `alarm-notify.sh`) may run before it is killed. Protects Alert evaluation from hung notification processes. Set to `0` to wait forever. | | postpone alarms during hibernation for | `1m` | Prevents false Alerts. May need to be increased if you get Alerts during hibernation. | | Health log retention | `5d` | Specifies the history of Alert events (in seconds) kept in the Agent's sqlite database. | | enabled alarms | * | Defines which Alerts to load from both user and stock directories. This is a [simple pattern](/docs/developer-and-contributor-corner/libnetdata/simple-patterns) list of Alert or template names. Can be used to disable specific Alerts. For example, `enabled alarms = !oom_kill *` will load all Alerts except `oom_kill`. | @@ -269,9 +271,9 @@ Use `yes` instead of `auto` in plugin configuration sections to enable these cha External plugins will have only two options at `netdata.conf`: -| setting | default | info | -|:---------------:|:--------------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| setting | default | info | +|:---------------:|:----------------------------------------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | update every | the value of `[db].update every` setting | The frequency in seconds the plugin should collect values. For more information check the [performance guide](/docs/netdata-agent/configuration/performance-optimization). | -| command options | - | Additional command line options to pass to the plugin. | +| command options | - | Additional command line options to pass to the plugin. | External plugins that need additional configuration may support a dedicated file in `/etc/netdata`. Check their documentation. diff --git a/docs/Netdata Agent/Configuration/Database.mdx b/docs/Netdata Agent/Configuration/Database.mdx index b911bad02c..40151c69ad 100644 --- a/docs/Netdata Agent/Configuration/Database.mdx +++ b/docs/Netdata Agent/Configuration/Database.mdx @@ -20,9 +20,11 @@ Use [`edit-config`](/docs/netdata-agent/configuration#edit-configuration-files) ```text [db] # dbengine, ram, none - mode = dbengine + db = dbengine ``` +`mode` is also accepted for backwards compatibility. + ## Tiers ### Retention Settings @@ -33,7 +35,7 @@ In a Parent-Child setup, these settings control the Parent's total storage for m Child and Parent storage are independent: -- A Child can keep local history based on its own `[db].mode`. +- A Child can keep local history based on its own `[db].db`. - Streamed metrics can also be persisted on the Parent, in the Parent's own dbengine files. Retention size is enforced **per-tier**, not per Child, so all streaming Children share the Parent's tier quota. For Parent sizing guidance, see [Parent Retention Sizing](/docs/netdata-agent/resource-utilization/disk-&-retention#parent-retention-sizing). @@ -58,7 +60,7 @@ You can change these limits using [`edit-config`](/docs/netdata-agent/configurat ```text [db] - mode = dbengine + db = dbengine storage tiers = 3 # Tier 0, per second data. Set to 0 for no limit. diff --git a/docs/Netdata Agent/Installation/Kubernetes Helm chart reference.mdx b/docs/Netdata Agent/Installation/Kubernetes Helm chart reference.mdx index 3d3757c1f2..9f4e7eeb62 100644 --- a/docs/Netdata Agent/Installation/Kubernetes Helm chart reference.mdx +++ b/docs/Netdata Agent/Installation/Kubernetes Helm chart reference.mdx @@ -12,7 +12,7 @@ slug: "/netdata-agent/installation/kubernetes-helm-chart-reference" Artifact HUB -![Version: 3.7.168](https://img.shields.io/badge/Version-3.7.168-informational?style=flat-square) +![Version: 3.7.169](https://img.shields.io/badge/Version-3.7.169-informational?style=flat-square) ![AppVersion: v2.10.3](https://img.shields.io/badge/AppVersion-v2.10.3-informational?style=flat-square) @@ -468,6 +468,15 @@ true The name of the service account to use. If not set and create is true, a name is generated using the fullname template + + serviceAccount.annotations + object + 
+\{}
+
+ + Annotations to add to the service account (e.g. an AWS IRSA `eks.amazonaws.com/role-arn`) + restarter.enabled bool diff --git a/docs/Netdata Agent/Resource Utilization/Disk & Retention.mdx b/docs/Netdata Agent/Resource Utilization/Disk & Retention.mdx index 060e22957e..a0829f45d5 100644 --- a/docs/Netdata Agent/Resource Utilization/Disk & Retention.mdx +++ b/docs/Netdata Agent/Resource Utilization/Disk & Retention.mdx @@ -21,6 +21,12 @@ Netdata offers two database modes to suit your needs for performance and data pe ## `dbengine` +:::note + +By default, `dbengine` stores its metrics database files on disk. The exact location depends on your installation method, operating system, and whether you run Netdata in Docker or Kubernetes — see [Backing up a Netdata Agent](/docs/netdata-agent/maintenance/backup-and-restore-an-agent) for the default path and other Netdata data locations. + +::: + Netdata's `dbengine` mode efficiently stores data on disk using compression. The actual disk space used depends on how well the data compresses. This mode uses a tiered storage approach: data is saved in multiple tiers on disk. Each tier retains data at a different resolution (detail level). Higher tiers store a down-sampled (less detailed) version of the data found in lower tiers. @@ -69,12 +75,12 @@ For details about how dbengine enforces retention size limits, see [Retention Si Child and Parent storage are independent: -- **On the Child (local):** Controlled by the Child's `[db].mode`. +- **On the Child (local):** Controlled by the Child's `[db].db`. - **On the Parent (received stream):** Controlled by the Parent's settings. Metrics streamed from Children can be persisted on the Parent and count against the Parent's per-tier retention limits. **Configuring dbengine mode and retention**: -- Enable dbengine mode: The dbengine mode is already the default, so no configuration change is necessary. For reference, the dbengine mode can be configured by setting `[db].mode` to `dbengine` in `netdata.conf`. +- Enable dbengine mode: The dbengine mode is already the default, so no configuration change is necessary. For reference, the dbengine mode can be configured by setting `[db].db` to `dbengine` in `netdata.conf`. - Adjust retention (optional): see [Change how long Netdata stores metrics](/docs/netdata-agent/configuration/database#tiers). ## `ram` @@ -87,5 +93,5 @@ The memory required per sample in these modes, is four bytes: `ram` mode uses `m **Configuring ram mode and retention**: -- Enable ram mode: To use in-memory storage, set `[db].mode` to ram in your `netdata.conf` file. Remember, this mode won't retain historical data after restarts. +- Enable ram mode: To use in-memory storage, set `[db].db` to ram in your `netdata.conf` file. Remember, this mode won't retain historical data after restarts. - Adjust retention (optional): While ram mode focuses on real-time data, you can optionally control the number of samples stored in memory. Set `[db].retention` in `netdata.conf` to the desired number in seconds. Note: If the value you choose isn't a multiple of 1024, Netdata will automatically round it up to the nearest multiple. diff --git a/docs/Netdata Parents/Configuration Examples.mdx b/docs/Netdata Parents/Configuration Examples.mdx index d7ac628003..215540db29 100644 --- a/docs/Netdata Parents/Configuration Examples.mdx +++ b/docs/Netdata Parents/Configuration Examples.mdx @@ -45,7 +45,7 @@ Edit `netdata.conf` on the Child using the [edit-config](/docs/netdata-agent/con [db] # https://github.com/netdata/netdata/blob/master/src/database/README.md # none = no retention, ram = some retention in ram - mode = ram + db = ram # The retention in seconds. # This provides some tolerance to the time the child has to find a parent # to transfer the data. For IoT, this can be lowered to 120. @@ -81,7 +81,6 @@ Edit `stream.conf` on the Child using the [edit-config](/docs/netdata-agent/conf **Perfect for:** IoT devices, containers, or any resource-constrained system. - ### Parent with Tiered Storage This example helps you configure a Parent with multiple [tiers of metrics storage](/docs/netdata-agent/database#tiers) to store different time ranges at different resolutions, for 10 Children with about 2k metrics each. Retention in each tier is restricted both in time and storage space, whichever is met first. See [retention settings](/docs/netdata-agent/configuration/database#retention-settings) for fine-tuning retention. @@ -101,7 +100,7 @@ Edit `netdata.conf` on the Parent using the [edit-config](/docs/netdata-agent/co ```ini [db] - mode = dbengine + db = dbengine dbengine tier backfill = new storage tiers = 3 dbengine page cache size = 1.4GiB @@ -142,7 +141,6 @@ Edit `stream.conf` on the Parent using the [edit-config](/docs/netdata-agent/con **Perfect for:** Central monitoring servers with enough storage for historical data. - ### Active-Active Parents This example guides you through setting up active-active Parents that sync with each other for high availability. @@ -196,7 +194,6 @@ This example guides you through setting up active-active Parents that sync with api key = API_KEY ``` - ## Further Reading We strongly recommend the following configuration changes for production deployments: diff --git a/docs/Netdata Parents/Parent Configuration Best Practices.mdx b/docs/Netdata Parents/Parent Configuration Best Practices.mdx index de7d4a5fab..74983dd794 100644 --- a/docs/Netdata Parents/Parent Configuration Best Practices.mdx +++ b/docs/Netdata Parents/Parent Configuration Best Practices.mdx @@ -150,7 +150,7 @@ Adding 5–15% overhead for replication buffers, indexes, and metadata, plan for ```ini [db] - mode = dbengine + db = dbengine update every = 1 storage tiers = 3 @@ -216,15 +216,15 @@ flowchart TB Netdata provides several benefits over other observability solutions: -| Advantage | Description | Value | -|-----------------------------------|--------------------------------------------|-----------------------------------------------------------------------| -| **Scalability & Flexibility** | Multiple independent Parents | Customized observability by region, service, or team | -| **Resilience & Reliability** | Built-in replication | Observability continues even if a Parent fails | -| **Optimized Cost & Performance** | Distributed workloads | Prevents bottlenecks and improves resource efficiency | -| **Ease of Use** | Minimal setup and maintenance | Reduces complexity and operational overhead | -| **On-Prem Control** | Data remains within your infrastructure | Enhanced security and compliance, even when using Netdata Cloud. For a fully self-hosted control plane, see [Netdata Cloud On-Prem](/docs/netdata-cloud-on-prem) | -| **Comprehensive Observability** | Segmented infrastructure with unified view | Deep visibility with tailored retention, alerts, and machine learning | -| **Predictable Capacity Planning** | Published per-metric storage cost | Allows accurate disk and hardware sizing for Parents | +| Advantage | Description | Value | +|-----------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| **Scalability & Flexibility** | Multiple independent Parents | Customized observability by region, service, or team | +| **Resilience & Reliability** | Built-in replication | Observability continues even if a Parent fails | +| **Optimized Cost & Performance** | Distributed workloads | Prevents bottlenecks and improves resource efficiency | +| **Ease of Use** | Minimal setup and maintenance | Reduces complexity and operational overhead | +| **On-Prem Control** | Data remains within your infrastructure | Enhanced security and compliance, even when using Netdata Cloud. For a fully self-hosted control plane, see [Netdata Cloud On-Prem](/docs/netdata-cloud-on-prem) | +| **Comprehensive Observability** | Segmented infrastructure with unified view | Deep visibility with tailored retention, alerts, and machine learning | +| **Predictable Capacity Planning** | Published per-metric storage cost | Allows accurate disk and hardware sizing for Parents | :::tip diff --git a/docs/Netdata Parents/Streaming Routing Reference.mdx b/docs/Netdata Parents/Streaming Routing Reference.mdx index 1bfc36f985..93fce9b843 100644 --- a/docs/Netdata Parents/Streaming Routing Reference.mdx +++ b/docs/Netdata Parents/Streaming Routing Reference.mdx @@ -90,10 +90,10 @@ Once connected, the child maintains a persistent connection: Netdata automatically replicates missing historical data when reconnection occurs. Data is only lost if: - Child restarts during disconnection AND -- Child uses `memory mode = ram` (metrics stored in memory) AND +- Child uses `[db].db = ram` (metrics stored in memory) AND - Disconnection exceeds retention period (default: 1 hour for RAM mode) -For persistent data, use `memory mode = dbengine`. +For persistent data, use `[db].db = dbengine`. ::: @@ -201,8 +201,8 @@ The **Netdata Streaming** function (under the "Functions" tab) provides: - Comprehensive overview of all streaming connections - Status, replication completion time, and connection details - Works on both parent and child nodes: - - **On child**: Shows outgoing connections - - **On parent**: Shows incoming connections (InHops = 1 for direct children, >1 for proxied connections) + - **On child**: Shows outgoing connections + - **On parent**: Shows incoming connections (InHops = 1 for direct children, >1 for proxied connections) #### Viewing Logs