[pull] master from netdata:master

CHANGELOG.md

@@ -6,6 +6,14 @@
 
 **Merged pull requests:**
 
+- docs: format, typos, and some simplifications in `docs/` [\#19112](https://github.com/netdata/netdata/pull/19112) ([ilyam8](https://github.com/ilyam8))
+- change dim order because of colours in reboot\_required [\#19111](https://github.com/netdata/netdata/pull/19111) ([ilyam8](https://github.com/ilyam8))
+- fix\(proc/reboot\_required\): disable on non Debian-based systems [\#19110](https://github.com/netdata/netdata/pull/19110) ([ilyam8](https://github.com/ilyam8))
+- feat\(proc.plugin\): add Reboot Required collector [\#19109](https://github.com/netdata/netdata/pull/19109) ([ilyam8](https://github.com/ilyam8))
+- docs: update On-Prem System Requirements [\#19107](https://github.com/netdata/netdata/pull/19107) ([ilyam8](https://github.com/ilyam8))
+- On-prem docs edits 2 [\#19105](https://github.com/netdata/netdata/pull/19105) ([Ancairon](https://github.com/Ancairon))
+- Docs edits on Cloud versions and On Prem [\#19104](https://github.com/netdata/netdata/pull/19104) ([Ancairon](https://github.com/Ancairon))
+- chore\(go.d/pkg/socket\): add err to callback return values [\#19103](https://github.com/netdata/netdata/pull/19103) ([ilyam8](https://github.com/ilyam8))
 - docs: fix img tag [\#19102](https://github.com/netdata/netdata/pull/19102) ([ilyam8](https://github.com/ilyam8))
 - Edit the organize doc [\#19101](https://github.com/netdata/netdata/pull/19101) ([Ancairon](https://github.com/Ancairon))
 - Update connecting documentation [\#19100](https://github.com/netdata/netdata/pull/19100) ([Ancairon](https://github.com/Ancairon))
@@ -439,12 +447,6 @@
 - go.d rename example =\> testrandom [\#18561](https://github.com/netdata/netdata/pull/18561) ([ilyam8](https://github.com/ilyam8))
 - Regenerate integrations.js [\#18560](https://github.com/netdata/netdata/pull/18560) ([netdatabot](https://github.com/netdatabot))
 - go.d/prometheus: add label\_prefix config option [\#18559](https://github.com/netdata/netdata/pull/18559) ([ilyam8](https://github.com/ilyam8))
-- Regenerate integrations.js [\#18558](https://github.com/netdata/netdata/pull/18558) ([netdatabot](https://github.com/netdatabot))
-- add nginx unit to apps\_groups.conf [\#18557](https://github.com/netdata/netdata/pull/18557) ([ilyam8](https://github.com/ilyam8))
-- go.d fix typesense/nginxunit meta [\#18556](https://github.com/netdata/netdata/pull/18556) ([ilyam8](https://github.com/ilyam8))
-- add go.d/nginxunit [\#18554](https://github.com/netdata/netdata/pull/18554) ([ilyam8](https://github.com/ilyam8))
-- fix some docs issues [\#18553](https://github.com/netdata/netdata/pull/18553) ([ilyam8](https://github.com/ilyam8))
-- go.d fix Goland code inspection warnings [\#18552](https://github.com/netdata/netdata/pull/18552) ([ilyam8](https://github.com/ilyam8))
 
 ## [v1.47.5](https://github.com/netdata/netdata/tree/v1.47.5) (2024-10-24)
 

CMakeLists.txt

@@ -1602,6 +1602,7 @@ set(PROC_PLUGIN_FILES
         src/collectors/proc.plugin/proc_sys_kernel_random_entropy_avail.c
         src/collectors/proc.plugin/proc_vmstat.c
         src/collectors/proc.plugin/proc_uptime.c
+        src/collectors/proc.plugin/run_reboot_required.c
         src/collectors/proc.plugin/proc_pressure.c
         src/collectors/proc.plugin/proc_pressure.h
         src/collectors/proc.plugin/sys_kernel_mm_ksm.c

docs/DICTIONARY.md

@@ -11,7 +11,7 @@ When the context is clear, we can omit the "Netdata" prefix for brevity.
 | **Agent** (**Agents**) | The core monitoring software that collects, processes and stores metrics |
 | **Daemon**             | The main Netdata process                                                 |
 | **Collector(s)**       | The various collectors of Netdata                                        |
-| **Registry**           | The default Netdata Registry, or any Agent acting as one                 ||
+| **Registry**           | The default Netdata Registry, or any Agent acting as one                 |
 
 ## Cloud
 
@@ -20,6 +20,7 @@ When the context is clear, we can omit the "Netdata" prefix for brevity.
 | **Cloud**             | The centralized platform for managing and visualizing Netdata metrics                 |
 | **Claim(ing) Token**  | The token used to Connect the Agent to the Cloud                                      |
 | **Connect(ing)(ion)** | The process of connecting the Agent to the Cloud. Do not use the word "claim" instead |
+| **Cloud On Prem**     | The version of Cloud we ship for Businesses that want to run it on premises           |
 
 ## Database
 
@@ -43,4 +44,4 @@ When the context is clear, we can omit the "Netdata" prefix for brevity.
 | **Model(s)**            |              | Uppercase when referring to the ML Models Netdata uses                                          |
 | **Anomaly Detection**   |              | The capability to identify unusual patterns in metrics                                          |
 | **Metric Correlations** |              | Filters dashboard to show metrics with the most significant changes in the selected time window |
-| **Anomaly Advisor**     |              | The interface and tooling for analyzing detected anomalies                                      |
+| **Anomaly Advisor**     |              | The interface and tooling for analyzing detected anomalies                                      |

docs/alerts-and-notifications/creating-alerts-with-netdata-alerts-configuration-manager.md

@@ -32,11 +32,11 @@ You can read more about the different options in the [Alerts reference documenta
 ### Alerting Conditions
 
 - **Thresholds**: Set thresholds for warning and critical Alert states, specifying whether the Alert should trigger above or below these thresholds. Advanced settings allow for custom formulas.
-  - **Recovery Thresholds**: Set thresholds for downgrading the Alert from critical to warning or from warning to clear.
+- **Recovery Thresholds**: Set thresholds for downgrading the Alert from critical to warning or from warning to clear.
 - **Check Interval**: Define how frequently the health check should run.
 - **Delay Notifications**: Manage notification delays for Alert escalations or de-escalations.
-- **Agent Specific Options**: Options exclusive to the Netdata Agent, like repeat notification frequencies and notification recipients.
-  - **Custom Exec Script**: Define custom scripts to execute when an Alert triggers.
+- **Agent-Specific Options**: Options exclusive to the Netdata Agent, like repeat notification frequencies and notification recipients.
+- **Custom Exec Script**: Define custom scripts to execute when an Alert triggers.
 
 ### Alert Name, Description, and Summary Section
 

docs/alerts-and-notifications/notifications/README.md

@@ -4,6 +4,6 @@ This section includes the documentation of the integrations for both of Netdata'
 
 <!-- following links are virtual links to a generated page, should not lead somewhere upon click from GitHub -->
 
-- Netdata Cloud provides centralized alert notifications, utilizing the health status data already sent to Netdata Cloud from connected nodes to send alerts to configured integrations. [Supported integrations](/docs/alerts-&-notifications/notifications/centralized-cloud-notifications) include Amazon SNS, Discord, Slack, Splunk, and others.
+- Netdata Cloud provides centralized alert notifications, using the health status data already sent to Netdata Cloud from connected nodes to send alerts to configured integrations. [Supported integrations](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications) include Amazon SNS, Discord, Slack, Splunk, and others.
 
-- The Netdata Agent offers a [wider range of notification options](/docs/alerts-&-notifications/notifications/agent-dispatched-notifications) directly from the Agent itself. You can choose from over a dozen services, including email, Slack, PagerDuty, Twilio, and others, for more granular control over notifications on each node.
+- The Netdata Agent offers a [wider range of notification options](/docs/alerts-and-notifications/notifications/agent-dispatched-notifications) directly from the Agent itself. You can choose from over a dozen services, including email, Slack, PagerDuty, Twilio, and others, for more granular control over notifications on each node.

docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-alert-notification-silencing-rules.md

@@ -7,12 +7,12 @@ From the Cloud interface, you can manage your space's Alert notification silenci
 To manage **space's Alert notification silencing rule settings**, you will need the following:
 
 - A Netdata Cloud account
-- Access to the space as an **administrator** or **manager** (**troubleshooters** can only view space rules)
+- Access to Space as an **administrator** or **manager** (**troubleshooters** can only view space rules)
 
 To manage your **personal Alert notification silencing rule settings**, you will need the following:
 
 - A Netdata Cloud account
-- Access to the space with any role except **billing**
+- Access to Space with any role except **billing**
 
 ### Steps
 
@@ -21,33 +21,33 @@ To manage your **personal Alert notification silencing rule settings**, you will
 3. Click on the **Notification Silencing Rules** tab.
 4. You will be presented with a table of the configured Alert notification silencing rules for:
 
-   - The space (if you aren't an **observer**)
-   - Yourself
+    - The space (if you aren't an **observer**)
+    - Yourself
 
    You will be able to:
 
-   1. **Add a new** Alert notification silencing rule configuration.
-      - Choose if it applies to **All users** or **Myself** (All users is only available for **administrators** and **managers**).
-      - You need to provide a name for the configuration so you can easily refer to it.
-      - Define criteria for Nodes, to which Rooms will the rule apply, on what Nodes and whether or not it applies to host labels key-value pairs.
-      - Define criteria for Alerts, such as Alert name is being targeted and on what Alert context. You can also specify if it will apply to a specific Alert role.
-      - Define when it will be applied:
-        - Immediately, from now until it is turned off or until a specific duration (start and end date automatically set).
-        - Scheduled, you can specify the start and end time for when the rule becomes active and then inactive (time is set according to your browser's local timezone).
-      Note: You are only able to add a rule if your space is on a [paid plan](/docs/netdata-cloud/view-plan-and-billing.md).
-   2. **Edit an existing** Alert notification silencing rule configuration. You will be able to change:
-      - The name provided for it
-      - Who it applies to
-      - Selection criteria for Nodes and Alerts
-      - When it will be applied
-   3. **Enable/Disable** a given Alert notification silencing rule configuration.
-      - Use the toggle to enable or disable
-   4. **Delete an existing** Alert notification silencing rule.
-      - Use the trash icon to delete your configuration
+    1. **Add a new** Alert notification silencing rule configuration.
+        - Choose if it applies to **All users** or **Myself** (All users is only available for **administrators** and **managers**).
+        - You need to provide a name for the configuration so you can refer to it.
+        - Define criteria for Nodes, to which Rooms will the rule apply, on what Nodes and whether it applies to host labels key-value pairs.
+        - Define criteria for Alerts, such as Alert name is being targeted and in what Alert context. You can also specify if it applies to a specific Alert role.
+        - Define when it is applied:
+            - Immediately, from now until it is turned off or until a specific duration (start and end date automatically set).
+            - Scheduled, you can specify the start and end time for when the rule becomes active and then inactive (time is set according to your browser's local timezone).
+              Note: You are only able to add a rule if your space is on a [paid plan](/docs/netdata-cloud/view-plan-and-billing.md).
+    2. **Edit an existing** Alert notification silencing rule configuration. You will be able to change:
+        - The name provided for it
+        - Who it applies to
+        - Selection criteria for Nodes and Alerts
+        - When it will be applied
+    3. **Enable/Disable** a given Alert notification silencing rule configuration.
+        - Use the toggle to enable or disable
+    4. **Delete an existing** Alert notification silencing rule.
+        - Use the trash icon to delete your configuration
 
 ## Silencing Rules Examples
 
-| Rule name                        | Rooms          | Nodes    | Host Label               | Alert name                                       | Alert context | Alert instance           | Alert role  | Description                                                                                                                                                                                                               |
+| Rule name                        | Rooms              | Nodes    | Host Label               | Alert name                                       | Alert context | Alert instance           | Alert role  | Description                                                                                                                                                                                                               |
 |:---------------------------------|:-------------------|:---------|:-------------------------|:-------------------------------------------------|:--------------|:-------------------------|:------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Space silencing                  | All Rooms          | *        | *                        | *                                                | *             | *                        | *           | This rule silences the entire space, targets all nodes, and for all users. E.g. infrastructure-wide maintenance window.                                                                                                   |
 | DB Servers Rooms                 | PostgreSQL Servers | *        | *                        | *                                                | *             | *                        | *           | This rule silences the nodes in the Room named PostgreSQL Servers, for example, it doesn't silence the `All Nodes` Room. E.g. My team with membership to this Room doesn't want to receive notifications for these nodes. |

docs/alerts-and-notifications/notifications/centralized-cloud-notifications/manage-notification-methods.md

@@ -9,7 +9,7 @@ From the Cloud interface, you can manage your Space's notification settings as w
 To manage Space notification settings, you will need the following:
 
 - A Netdata Cloud account
-- Access to the Space as an **administrator**
+- Access to Space as an **administrator**
 
 ### Available Actions per Notification Method Based on Service Level
 
@@ -31,20 +31,20 @@ To manage Space notification settings, you will need the following:
 2. Click on the **Alerts & Notifications** tab on the left-hand side.
 3. Click on the **Notification Methods** tab.
 4. You will be presented with a table of the configured notification methods for the Space. You will be able to:
-   1. **Add a new** notification method configuration.
-      - Choose the service from the list of available ones. The available options will depend on your subscription plan.
-      - You can optionally provide a name for the configuration so you can easily refer to it.
-      - You can define the filtering criteria, regarding which Rooms the method will apply, and what notifications you want to receive (All Alerts and unreachable, All Alerts, Critical only).
-      - Depending on the service, different inputs will be present. Please note that there are mandatory and optional inputs.
-         - If you have doubts on how to configure the service, you can find a link at the top of the modal that takes you to the specific documentation page to help you.
-   2. **Edit an existing** notification method configuration. Personal level ones can't be edited here, see [Manage User Notification Settings](#manage-user-notification-settings). You will be able to change:
-      - The name provided for it
-      - Filtering criteria
-      - Service-specific inputs
-   3. **Enable/Disable** a given notification method configuration.
-      - Use the toggle to enable or disable the notification method configuration.
-   4. **Delete an existing** notification method configuration. Netdata provided ones can't be deleted, e.g., Email.
-      - Use the trash icon to delete your configuration.
+    1. **Add a new** notification method configuration.
+        - Choose the service from the list of available ones. The available options will depend on your subscription plan.
+        - You can optionally provide a name for the configuration so you can refer to it.
+        - You can define the filtering criteria, regarding which Rooms the method will apply, and what notifications you want to receive (All Alerts and unreachable, All Alerts, Critical only).
+        - Depending on the service, different inputs will be present. Please note that there are mandatory and optional inputs.
+            - If you have doubts on how to configure the service, you can find a link at the top of the modal that takes you to the specific documentation page to help you.
+    2. **Edit an existing** notification method configuration. Personal level ones can't be edited here, see [Manage User Notification Settings](#manage-user-notification-settings). You will be able to change:
+        - The name provided for it
+        - Filtering criteria
+        - Service-specific inputs
+    3. **Enable/Disable** a given notification method configuration.
+        - Use the toggle to enable or disable the notification method configuration.
+    4. **Delete an existing** notification method configuration. Netdata provided ones can't be deleted, e.g., Email.
+        - Use the trash icon to delete your configuration.
 
 ## Manage User Notification Settings
 
@@ -61,11 +61,11 @@ Note: If an administrator has disabled a Personal [service level](/docs/alerts-a
 
 1. Click on the **User notification settings** shortcut on top of the help button.
 2. You are presented with:
-   - The Personal [service level](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-level) notification methods you can manage.
-   - The list of Spaces and Rooms inside those where you have access to.
+    - The Personal [service level](/docs/alerts-and-notifications/notifications/centralized-cloud-notifications/centralized-cloud-notifications-reference.md#service-level) notification methods you can manage.
+    - The list of Spaces and Rooms inside those where you have access to.
 3. On this modal you will be able to:
-   1. **Enable/Disable** the notification method for you; this applies across all Spaces and Rooms.
-      - Use the toggle to enable or disable the notification method.
-   2. **Define what notifications you want** per Space/Room: All Alerts and unreachable, All Alerts, Critical only, or No notifications.
-   3. **Activate notifications** for a Room you aren't a member of.
-      - From the **All Rooms** tab, click on the Join button for the Room(s) you want.
+    1. **Enable/Disable** the notification method for you; this applies across all Spaces and Rooms.
+        - Use the toggle to enable or disable the notification method.
+    2. **Define what notifications you want** per Space/Room: All Alerts and unreachable, All Alerts, Critical only, or No notifications.
+    3. **Activate notifications** for a Room you aren't a member of.
+        - From the **All Rooms** tab, click on the Join button for the Room(s) you want.