Merge pull request #2465 from netdata/ingest

Author: ilyam8

docs/ai-and-machine-learning/mcp-integration.mdx

@@ -15,6 +15,12 @@ The Netdata MCP Server preview is live. [Get early access](https://b6yi53u6qjm.t
 
 :::
 
+:::note
+
+This integration leverages new and evolving AI technologies. While Netdata provides comprehensive infrastructure monitoring capabilities, the AI analysis features **depend on external AI services** and their inherent limitations. The quality and accuracy of AI-generated insights are **subject to the capabilities and constraints of the underlying AI models, not Netdata's monitoring functionality**.
+
+:::
+
 ## What is MCP?
 
 **Model Context Protocol (MCP)** is a new open standard that allows AI assistants to connect directly to your data sources and tools. Think of it as a bridge that lets AI systems access and analyze your real-time infrastructure data instead of just providing generic advice.
@@ -47,11 +53,11 @@ Instead of spending hours analyzing charts during an incident, you can now:
 
 ### Real-World Example
 
-**The Problem**: EMQX message broker goes down, affecting multiple services across your infrastructure.
+**The Problem**: Database server goes down, affecting multiple applications across your infrastructure.
 
 ```mermaid
 flowchart TD
-    A("🚨 EMQX Outage Occurs")
+    A("🚨 Database Outage Occurs")
     
     B("📊 Traditional Approach")
     C("🤖 Netdata + MCP")
@@ -132,11 +138,12 @@ Your AI assistant can:
 
 ## The Future of Infrastructure Monitoring
 
-With Netdata MCP, we're moving toward a future where:
+With Netdata MCP, we're moving toward a future where **AI understands your infrastructure** as well as your best engineers. **Troubleshooting becomes conversational** rather than manual chart analysis, **post-mortems write themselves** with complete root cause analysis, and **your monitoring system becomes a true team member** that helps solve problems.
 
-- **AI understands your infrastructure** as well as your best engineers
-- **Troubleshooting becomes conversational** rather than manual chart analysis
-- **Post-mortems write themselves** with complete root cause analysis
-- **Your monitoring system becomes a team member** that helps solve problems
+:::note
+
+This represents our vision for the future of infrastructure monitoring. While we're making significant progress with MCP integration, these capabilities are aspirational goals we're working toward, not current product features. For now, we are building the foundations for the reality we want to create.
+
+:::
 
 **Join us in pioneering the next generation of intelligent infrastructure monitoring.**

docs/collecting-metrics/Hardware Devices and Sensors/S.M.A.R.T..mdx

@@ -184,6 +184,7 @@ The following options can be defined globally: update_every.
 | scan_every | interval for discovering new devices using `smartctl --scan`, measured in seconds. Set to 0 to scan devices only once on startup. | 900 | no |
 | poll_devices_every | interval for gathering data for every device, measured in seconds. Data is cached for this interval. | 300 | no |
 | device_selector | Specifies a pattern to match the 'info name' of devices as reported by `smartctl --scan --json`. | * | no |
+| concurrent_scans | Number of devices to scan concurrently. Set to 0 for sequential scanning (default behavior). Improves performance when monitoring many devices. | 0 | no |
 | extra_devices | Allows manual specification of devices not automatically detected by `smartctl --scan`. Each device entry must include both a name and a type. See "Configuration Examples" for details. | [] | no |
 | no_check_power_mode | Skip data collection when the device is in a low-power mode. Prevents unnecessary disk spin-up. | standby | no |
 
@@ -218,6 +219,22 @@ jobs:
 ```
 </details>
 
+##### Concurrent scanning for multiple devices
+
+This example demonstrates enabling concurrent scanning to improve performance when monitoring many devices.
+
+
+<details open>
+<summary>Config</summary>
+
+```yaml
+jobs:
+  - name: smartctl
+    concurrent_scans: 4  # Scan up to 4 devices concurrently
+
+```
+</details>
+
 ##### Extra devices
 
 This example demonstrates using `extra_devices` to manually add a storage device (`/dev/sdc`) not automatically detected by `smartctl --scan`.

docs/netdata-agent/installation/kubernetes-helm-chart-reference.mdx

@@ -11,9 +11,9 @@ learn_link: "https://learn.netdata.cloud/docs/netdata-agent/installation/kuberne
 
 <a href="https://artifacthub.io/packages/search?repo=netdata" target="_blank" rel="noopener noreferrer"><img loading="lazy" src="https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/netdata" alt="Artifact HUB" class="img_node_modules-@docusaurus-theme-classic-lib-theme-MDXComponents-Img-styles-module"></img></a>
 
-<img src="https://img.shields.io/badge/Version-3.7.139-informational" alt="Version: 3.7.139"></img>
+<img src="https://img.shields.io/badge/Version-3.7.140-informational" alt="Version: 3.7.140"></img>
 
-<img loading="lazy" src="https://img.shields.io/badge/AppVersion-v2.5.3-informational" alt="AppVersion: v2.5.3" class="img_node_modules-@docusaurus-theme-classic-lib-theme-MDXComponents-Img-styles-module"></img>
+<img loading="lazy" src="https://img.shields.io/badge/AppVersion-v2.5.4-informational" alt="AppVersion: v2.5.4" class="img_node_modules-@docusaurus-theme-classic-lib-theme-MDXComponents-Img-styles-module"></img>
 
 _Based on the work of varyumin (https://github.com/varyumin/netdata)_.
 

docs/netdata-cloud-on-prem/security-hardening-guide.mdx

@@ -9,8 +9,6 @@ learn_link: "https://learn.netdata.cloud/docs/netdata-cloud-on-prem/security-har
 
 # Security Hardening Guide for Netdata Cloud On-Prem
 
-# Security Hardening Guide for Netdata Cloud On-Prem
-
 ## Table of Contents
 
 - [Introduction](#introduction)