netdata · Ancairon · Jul 23, 2026 · Jul 22, 2026
diff --git a/docs/Alerts & Notifications/Notifications/Notifications.mdx b/docs/Alerts & Notifications/Notifications/Notifications.mdx
@@ -128,6 +128,15 @@ Netdata ships with hundreds of pre-configured alerts. You can also create your o
 - **[Alerts Configuration Manager](/docs/alerts-&-notifications/creating-alerts-with-the-alerts-configuration-manager)** — Visual UI wizard for creating and editing alerts
 - **[Manual configuration](/docs/alerts-&-notifications/alert-configuration-reference)** — Edit `health.d/*.conf` files directly for full control over alert syntax
 
+## On-Call Rotations and Escalation
+
+Netdata does not provide a native on-call rotation, escalation, or shift-scheduling engine. These capabilities are handled by the dedicated incident-management integrations that Netdata delivers alerts to.
+
+- **From the Agent:** incident-management and incident-response integrations such as [PagerDuty](/docs/alerts-&-notifications/notifications/agent-dispatched-notifications/pagerduty), [Opsgenie](/docs/alerts-&-notifications/notifications/agent-dispatched-notifications/opsgenie), [SIGNL4](/docs/alerts-&-notifications/notifications/agent-dispatched-notifications/signl4), and [ilert](/docs/alerts-&-notifications/notifications/agent-dispatched-notifications/ilert), where you define on-call schedules, escalation policies, and shift rotations. See the full list of [supported Agent integrations](https://learn.netdata.cloud/docs/alerts-&-notifications/notifications/agent-dispatched-notifications).
+- **From Cloud:** PagerDuty is available as a [paid-plan notification method](/docs/alerts-&-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference#service-classification).
+
+To use on-call rotations, configure one of these integrations to receive your Netdata alerts, then set up your rotations, escalation policies, and shift schedules inside that service. To change where alerts are sent, see [Notification Methods](#notification-methods) or the [Cloud notification methods](/docs/alerts-&-notifications/notifications/centralized-cloud-notifications/manage-notification-methods) guide.
+
 ## Next Steps
 
 - [Set up Cloud Notifications](/docs/alerts-&-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference)

diff --git a/docs/Collecting Metrics/Collectors/Storage and Filesystems/SMB Server Shares.mdx b/docs/Collecting Metrics/Collectors/Storage and Filesystems/SMB Server Shares.mdx
@@ -43,7 +43,7 @@ This collector only supports collecting metrics from a single instance of this i
 
 #### Auto-Detection
 
-This collector is disabled by default. When enabled, it automatically detects all available SMB share instances and metrics.
+This collector is enabled by default and automatically detects all available SMB share instances and metrics. On systems where the 'SMB Server Shares' object is not available, no SMB metrics are collected.
 
 
 #### Limits

diff --git a/docs/Collecting Metrics/StatsD.mdx b/docs/Collecting Metrics/StatsD.mdx
@@ -345,6 +345,40 @@ This structure allows for flexible and powerful metric configuration within Netd
 - **`update every (flushInterval) = 1s`** - How often StatsD updates Netdata charts
 - **`decimal detail = 1000`** - Controls decimal precision in gauges and histograms
 
+### Accepting metrics from another machine (LAN/remote host)
+
+By default, Netdata's StatsD listener binds only to `localhost`, so it accepts metrics from applications running on the **same machine** as the Netdata Agent. To accept metrics from another machine on your network, change the `bind to` setting in the `[statsd]` section of `netdata.conf`.
+
+1. Open the StatsD configuration:
+
+   ```bash
+   sudo ./edit-config netdata.conf
+   ```
+
+2. In the `[statsd]` section, set `bind to` to the Netdata host's LAN IP address (for example, `192.168.1.10`):
+
+   ```
+   [statsd]
+   	bind to = udp:192.168.1.10:8125 tcp:192.168.1.10:8125
+   ```
+
+   To listen on all interfaces instead of a single IP, bind to `0.0.0.0`:
+
+   ```
+   [statsd]
+   	bind to = udp:0.0.0.0:8125 tcp:0.0.0.0:8125
+   ```
+
+3. [Restart](/docs/netdata-agent/maintenance/service-control) the Agent so the new binding takes effect.
+
+4. On the sending machine, point your application's StatsD client at the Netdata host's IP address and port `8125`, using either UDP or TCP. For client library examples, see [Using StatsD with Different Languages](#using-statsd-with-different-languages).
+
+:::warning
+
+Binding `bind to` to `0.0.0.0` or a routable network interface exposes port `8125` to other hosts on the network. Restrict access with a firewall that only allows connections from your trusted machines, and avoid binding to public-facing interfaces.
+
+:::
+
 ## StatsD Charts
 
 Netdata can visualize StatsD collected metrics in two ways:

diff --git a/docs/Dashboards and Charts/Charts.mdx b/docs/Dashboards and Charts/Charts.mdx
@@ -78,11 +78,14 @@ A **context** groups charts by metric type and displayed dimensions. Contexts de
 
 - `apps.cpu` for **Apps CPU Time**
 - `apps.mem` for **Apps Real Memory**
+- `net.net` for **network Bandwidth**
 
 The part before the dot (`.`) is the **type**, while the part after is defined by the chart’s developer or its family.
 
 Contexts are also used for alert configurations.
 
+The contexts available on any given node depend on which collectors are enabled and what hardware and software Netdata detects, so there is no fixed universal list. To discover the contexts on your own system, browse the [Metrics tab](/docs/dashboards-and-charts/tabs/metrics) — charts there are grouped into sections by context — open the **Chart info** dialog on any chart to see its context value, or query the `/api/v3/contexts` endpoint programmatically. Each collector documents the metrics and contexts it produces on its integration page, which you can browse through the **Integrations tab** in the dashboard.
+
 ### Families
 
 A **family** represents a specific instance of a hardware or software resource that needs its own chart.
@@ -187,12 +190,12 @@ The **Group by** dropdown allows you to apply different grouping strategies on t
 
 ![Group by dropdown](https://user-images.githubusercontent.com/43294513/235468819-3af5a1d3-8619-48fb-a8b7-8e8b4cf6a8ff.png)
 
-| Grouping Option    | Description                                                |
-|--------------------|------------------------------------------------------------|
+| Grouping Option    | Description                                                                                               |
+|--------------------|-----------------------------------------------------------------------------------------------------------|
 | Group by Node      | Display each node (hostname) as a separate labeled dimension in the chart legend, with one entry per node |
-| Group by Instance  | Summarize data by instance with one dimension per instance |
-| Group by Dimension | Aggregate data across all nodes by dimension               |
-| Group by Label     | Summarize data based on label values                       |
+| Group by Instance  | Summarize data by instance with one dimension per instance                                                |
+| Group by Dimension | Aggregate data across all nodes by dimension                                                              |
+| Group by Label     | Summarize data based on label values                                                                      |
 
 :::tip
 
@@ -229,11 +232,11 @@ Each chart has a default aggregation function, which you can adjust as needed:
 
 When selecting aggregation functions over time, charts may offer dropdown menus for **Percentiles** and **Trimmed Mean / Median** selection. Below are examples of these dropdowns:
 
-### Percentile Selection Example:
+### Percentile Selection Example
 
 ![Percentile selection dropdown](https://user-images.githubusercontent.com/70198089/236410299-de5f3367-f3b0-4beb-a73f-a49007c543d4.png)
 
-### Trimmed Mean / Median Selection Example:
+### Trimmed Mean / Median Selection Example
 
 ![Trimmed Mean or Median selection dropdown](https://user-images.githubusercontent.com/70198089/236410858-74b46af9-280a-4ab2-ad26-5a6aa9403aa8.png)
 

diff --git a/...or Corner/Build the Netdata Agent Yourself/Build the Netdata Agent Yourself.mdx b/...or Corner/Build the Netdata Agent Yourself/Build the Netdata Agent Yourself.mdx
@@ -3,7 +3,7 @@ custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/developer-
 sidebar_label: "Build the Netdata Agent Yourself"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner/Build the Netdata Agent Yourself"
-sidebar_position: "190"
+sidebar_position: "200"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/build-the-netdata-agent-yourself"
 slug: "/developer-and-contributor-corner/build-the-netdata-agent-yourself"
 ---

diff --git a/docs/Developer and Contributor Corner/Community code of conduct.mdx b/docs/Developer and Contributor Corner/Community code of conduct.mdx
@@ -3,7 +3,7 @@ custom_edit_url: "https://github.com/netdata/.github/edit/main/CODE_OF_CONDUCT.m
 sidebar_label: "Community code of conduct"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner"
-sidebar_position: "50"
+sidebar_position: "60"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/community-code-of-conduct"
 slug: "/developer-and-contributor-corner/community-code-of-conduct"
 ---

diff --git a/...utor Corner/Contribute to the documentation/Contribute to the documentation.mdx b/...utor Corner/Contribute to the documentation/Contribute to the documentation.mdx
@@ -3,7 +3,7 @@ custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/guidelines
 sidebar_label: "Contribute to the documentation"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner/Contribute to the documentation"
-sidebar_position: "80"
+sidebar_position: "90"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/contribute-to-the-documentation"
 slug: "/developer-and-contributor-corner/contribute-to-the-documentation"
 ---

diff --git a/docs/Developer and Contributor Corner/Contributing.mdx b/docs/Developer and Contributor Corner/Contributing.mdx
@@ -3,7 +3,7 @@ custom_edit_url: "https://github.com/netdata/.github/edit/main/CONTRIBUTING.md"
 sidebar_label: "Contributing"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner"
-sidebar_position: "40"
+sidebar_position: "50"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/contributing"
 slug: "/developer-and-contributor-corner/contributing"
 ---

diff --git a/docs/Developer and Contributor Corner/Database Engine.mdx b/docs/Developer and Contributor Corner/Database Engine.mdx
@@ -3,7 +3,7 @@ custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/database/en
 sidebar_label: "Database Engine"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner"
-sidebar_position: "30"
+sidebar_position: "40"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/database-engine"
 slug: "/developer-and-contributor-corner/database-engine"
 ---
@@ -127,6 +127,8 @@ data from lower tiers, so that the aggregation they provide will be accurate.
 Configuring how the number of tiers and the disk space allocated to each tier is how you can
 [change how long netdata stores metrics](/docs/netdata-agent/configuration/database#tiers).
 
+For how `update every` controls each tier's granularity and interacts with retention time and disk size, see [Update Every and Tier Granularity](/docs/netdata-agent/configuration/database#update-every-and-tier-granularity).
+
 ### Data loss
 
 Until **hot pages** and **dirty pages** are **flushed** to disk, they are at risk (e.g., due to a crash, or

diff --git a/docs/Developer and Contributor Corner/Dynamic Configuration.mdx b/docs/Developer and Contributor Corner/Dynamic Configuration.mdx
@@ -3,7 +3,7 @@ custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/developer-
 sidebar_label: "Dynamic Configuration"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner"
-sidebar_position: "20"
+sidebar_position: "30"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/dynamic-configuration"
 slug: "/developer-and-contributor-corner/dynamic-configuration"
 ---

diff --git a/docs/Developer and Contributor Corner/External Plugins/External Plugins.mdx b/docs/Developer and Contributor Corner/External Plugins/External Plugins.mdx
@@ -3,7 +3,7 @@ custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/plugins.d/R
 sidebar_label: "External Plugins"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner/External Plugins"
-sidebar_position: "70"
+sidebar_position: "80"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/external-plugins"
 slug: "/developer-and-contributor-corner/external-plugins"
 ---

diff --git a/docs/Developer and Contributor Corner/Glossary.mdx b/docs/Developer and Contributor Corner/Glossary.mdx
@@ -3,7 +3,7 @@ custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/glossary.m
 sidebar_label: "Glossary"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner"
-sidebar_position: "90"
+sidebar_position: "100"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/glossary"
 slug: "/developer-and-contributor-corner/glossary"
 ---

diff --git a/docs/Developer and Contributor Corner/Health command API tester.mdx b/docs/Developer and Contributor Corner/Health command API tester.mdx
@@ -3,7 +3,7 @@ custom_edit_url: "https://github.com/netdata/netdata/edit/master/tests/health_mg
 sidebar_label: "Health command API tester"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner"
-sidebar_position: "130"
+sidebar_position: "140"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/health-command-api-tester"
 slug: "/developer-and-contributor-corner/health-command-api-tester"
 ---

diff --git a/docs/Developer and Contributor Corner/Import export and print a snapshot.mdx b/docs/Developer and Contributor Corner/Import export and print a snapshot.mdx
@@ -4,7 +4,7 @@ sidebar_label: "Import, export, and print a snapshot"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner"
 description: "Snapshots can be incredibly useful for diagnosing anomalies after they've already happened, and are interoperable with any other node running Netdata."
-sidebar_position: "140"
+sidebar_position: "150"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/import-export-and-print-a-snapshot"
 slug: "/developer-and-contributor-corner/import-export-and-print-a-snapshot"
 ---

diff --git a/...eloper and Contributor Corner/Install the Netdata Agent from a Git checkout.mdx b/...eloper and Contributor Corner/Install the Netdata Agent from a Git checkout.mdx
@@ -4,7 +4,7 @@ sidebar_label: "Install the Netdata Agent from a Git checkout"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner"
 description: "Use the Netdata Agent source code from GitHub, plus helper scripts to set up your system, to install Netdata without packages or binaries."
-sidebar_position: "200"
+sidebar_position: "210"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/install-the-netdata-agent-from-a-git-checkout"
 slug: "/developer-and-contributor-corner/install-the-netdata-agent-from-a-git-checkout"
 ---

diff --git a/...ontributor Corner/Monitor Nginx or Apache web server log files with Netdata.mdx b/...ontributor Corner/Monitor Nginx or Apache web server log files with Netdata.mdx
@@ -3,7 +3,7 @@ custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/developer-
 sidebar_label: "Monitor Nginx or Apache web server log files with Netdata"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner"
-sidebar_position: "150"
+sidebar_position: "160"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/monitor-nginx-or-apache-web-server-log-files-with-netdata"
 slug: "/developer-and-contributor-corner/monitor-nginx-or-apache-web-server-log-files-with-netdata"
 ---

diff --git a/docs/Developer and Contributor Corner/Monitor Unbound DNS servers with Netdata.mdx b/docs/Developer and Contributor Corner/Monitor Unbound DNS servers with Netdata.mdx
@@ -3,7 +3,7 @@ custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/developer-
 sidebar_label: "Monitor Unbound DNS servers with Netdata"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner"
-sidebar_position: "160"
+sidebar_position: "170"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/monitor-unbound-dns-servers-with-netdata"
 slug: "/developer-and-contributor-corner/monitor-unbound-dns-servers-with-netdata"
 ---

diff --git a/docs/Developer and Contributor Corner/Monitor a Hadoop cluster with Netdata.mdx b/docs/Developer and Contributor Corner/Monitor a Hadoop cluster with Netdata.mdx
@@ -3,7 +3,7 @@ custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/developer-
 sidebar_label: "Monitor a Hadoop cluster with Netdata"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner"
-sidebar_position: "170"
+sidebar_position: "180"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/monitor-a-hadoop-cluster-with-netdata"
 slug: "/developer-and-contributor-corner/monitor-a-hadoop-cluster-with-netdata"
 ---

diff --git a/...ibutor Corner/Monitor troubleshoot and debug applications with eBPF metrics.mdx b/...ibutor Corner/Monitor troubleshoot and debug applications with eBPF metrics.mdx
@@ -4,7 +4,7 @@ sidebar_label: "Monitor, troubleshoot, and debug applications with eBPF metrics"
 learn_status: "Published"
 learn_rel_path: "Developer and Contributor Corner"
 description: "Use Netdata's built-in eBPF metrics collector to monitor, troubleshoot, and debug your custom application using low-level kernel feedback."
-sidebar_position: "180"
+sidebar_position: "190"
 learn_link: "https://learn.netdata.cloud/docs/developer-and-contributor-corner/monitor-troubleshoot-and-debug-applications-with-ebpf-metrics"
 slug: "/developer-and-contributor-corner/monitor-troubleshoot-and-debug-applications-with-ebpf-metrics"
 ---