@cryptotaxi247 / netdata / commits / e58dac0d4

move whole category and fix leftovers (#20951)

* move whole category and fix leftovers * re-arrange files

Fotis Voutsas committed Sep 10, 2025 at 11:01 UTC e58dac0d4c082e325831dab0cef908c1d98ce9fc
2 files changed +8 -118
docs/.map/map.csv
+8 -15
@@ -2,18 +2,11 @@ custom_edit_url,sidebar_label,learn_status,learn_rel_path,description
2 https://github.com/netdata/netdata/edit/master/docs/welcome-to-netdata.md,Welcome to Netdata,Published,Welcome to Netdata,
3 https://github.com/netdata/netdata/edit/master/docs/netdata-enterprise-evaluation-corrected.md,Enterprise Evaluation Guide,Published,Welcome to Netdata,
4 https://github.com/netdata/netdata/edit/master/docs/getting-started-netdata/guide.md,Getting Started,Published,root,
5 -https://github.com/netdata/netdata/edit/master/docs/deployment-guides/README.md,Deployment Guides,Published,Deployment Guides,
6 -https://github.com/netdata/netdata/edit/master/docs/deployment-guides/standalone-deployment.md,Single Agent,Published,Deployment Guides,
7 -https://github.com/netdata/netdata/edit/master/docs/deployment-guides/deployment-with-centralization-points.md,Parent-Child,Published,Deployment Guides,
8 -https://github.com/netdata/netdata/edit/master/docs/observability-centralization-points/best-practices.md,Parent Configuration Best Practices,Published,Deployment Guides,
9 -https://github.com/netdata/netdata/edit/master/src/streaming/README.md,Parent-Child Configuration Reference,Published,Deployment Guides,
10 -https://github.com/netdata/netdata/edit/master/docs/deployment-guides/deployment-strategies.md,Configuration Examples,Published,Deployment Guides,
11 -https://github.com/netdata/netdata/edit/master/docs/streaming-routing.md,Streaming Routing Reference,Published,Deployment Guides,
12 -https://github.com/netdata/netdata/edit/master/docs/nodes-ephemerality.md,Node Types and Lifecycle Reference,Published,Deployment Guides,
5 https://github.com/netdata/netdata/edit/master/docs/Demo-Sites.md,Live Demo,Published,root,
6 ,,,,
15 -https://github.com/netdata/netdata/edit/master/docs/netdata-agent/README.md,Netdata Agent,Published,Netdata Agent,
7 +https://github.com/netdata/netdata/edit/master/docs/deployment-guides/standalone-deployment.md,Netdata Agent,Published,Netdata Agent,
8 https://github.com/netdata/netdata/edit/master/docs/netdata-agent/versions-and-platforms.md,Versions & Platforms,Published,Netdata Agent,Present all the supported platform in the Netdata solution
9 +https://github.com/netdata/netdata/edit/master/docs/deployment-guides/README.md,Quickstart Deployment,Published,Netdata Agent,
10 https://github.com/netdata/netdata/edit/master/packaging/installer/README.md,Installation,Published,Netdata Agent/Installation,
11 https://github.com/netdata/netdata/edit/master/packaging/installer/methods/kickstart.md,Linux,Published,Netdata Agent/Installation/Linux,"The kickstart.sh script installs Netdata from source, including all dependencies required to connect to Netdata Cloud, with a single command."
12 https://github.com/netdata/netdata/edit/master/packaging/installer/methods/packages.md,Native Linux Distribution packages,Published,Netdata Agent/Installation/Linux,Instructions for how to install Netdata using native DEB or RPM packages.
@@ -74,12 +67,12 @@ https://github.com/netdata/netdata/edit/master/docs/netdata-agent/configuration/
67 ,,,,
68 ,,,,
69 ,,,,
77 -,,,,
78 -,,,,
79 -,,,,
80 -,,,,
81 -,,,,
82 -,,,,
70 +https://github.com/netdata/netdata/edit/master/docs/deployment-guides/deployment-with-centralization-points.md,Netdata Parents,Published,Netdata Parents,
71 +https://github.com/netdata/netdata/edit/master/docs/observability-centralization-points/best-practices.md,Parent Configuration Best Practices,Published,Netdata Parents,
72 +https://github.com/netdata/netdata/edit/master/src/streaming/README.md,Parent-Child Configuration Reference,Published,Netdata Parents,
73 +https://github.com/netdata/netdata/edit/master/docs/deployment-guides/deployment-strategies.md,Configuration Examples,Published,Netdata Parents,
74 +https://github.com/netdata/netdata/edit/master/docs/streaming-routing.md,Streaming Routing Reference,Published,Netdata Parents,
75 +https://github.com/netdata/netdata/edit/master/docs/nodes-ephemerality.md,Node Types and Lifecycle Reference,Published,Netdata Parents,
76 ,,,,
77 ,,,,
78 https://github.com/netdata/netdata/edit/master/docs/netdata-cloud/README.md,Netdata Cloud,Published,Netdata Cloud,
docs/netdata-agent/README.md deleted
-103
@@ -1,103 +0,0 @@
1 -# Netdata Agent
2 -
3 -The Netdata Agent is the main building block in the Netdata ecosystem. You install it on all monitored systems to monitor system components, containers, and applications.
4 -
5 -The Netdata Agent is an **observability pipeline in a box** that you can either operate standalone, or blend into a bigger pipeline made by more Netdata Agents (Children and Parents).
6 -
7 -## Distributed Observability Pipeline
8 -
9 -Your Netdata observability pipeline looks like in the following graph.
10 -
11 -You can extend the pipeline by creating Metrics Observability Centralization Points that are linked all together (`from a remote Netdata`, `to a remote Netdata`), so that all Netdata you install become a vast integrated observability pipeline.
12 -
13 -<details>
14 -<summary><strong>Click to see visual representation of the observability pipeline</strong></summary>
15 -
16 -```mermaid
17 -flowchart TD
18 - Start(["<b>Remote Netdata Input</b>"]) --> Discover
19 - LocalAgent["<b>Local Netdata Agent</b>"] --> Discover
20 - Discover["<b>Discover</b><br/>Auto-detect metric sources<br/>Auto-discover on Kubernetes"] --> Collect
21 - Collect["<b>Collect</b><br/>Query data sources<br/>800+ integrations<br/>OpenMetrics, StatsD"] --> Detect
22 - Detect["<b>Detect Anomalies</b><br/>Machine learning models<br/>Real-time outlier detection"] --> Store
23 - Store["<b>Store</b><br/>Time-series database<br/>Anomaly status tracking"] --> Learn
24 - Store --> Check
25 - Store --> Query
26 - Store --> Score
27 - Store --> Stream
28 - Store --> Export
29 - Learn["<b>Learn</b><br/>Train ML models<br/>Behavior patterns"] --> Detect
30 - Check["<b>Check</b><br/>Health engine<br/>Alert triggering"] --> Alerts
31 - Query["<b>Query</b><br/>Time-series data queries"] --> Visualize
32 - Score["<b>Score</b><br/>Metric comparison<br/>Correlation analysis"] --> Visualize
33 - Query --> MCP
34 - Score --> MCP
35 - Alerts["<b>Alert Transitions</b>"] --> Notifications
36 - Stream --> End(["<b>Remote Netdata Output</b>"])
37 - Export --> ThirdParty
38 - Visualize --> Dashboard
39 - MCP --> AIAssistant
40 - ThirdParty["<b>Third-party DBs</b><br/>External systems"] --> ExternalDash
41 - Dashboard["<b>Netdata Dashboards</b><br/>Real-time visualization"]
42 - AIAssistant["<b>AI Assistant</b><br/>Intelligent analysis"]
43 - ExternalDash["<b>Third-party Dashboards</b><br/>Grafana, etc."]
44 - Notifications["<b>Alert Notifications</b><br/>Multi-channel delivery"]
45 - classDef input fill: #e8f4fd, stroke: #4a90e2, stroke-width: 3px, color: #2c3e50, rx: 15, ry: 15, font-size: 14px
46 - classDef process fill: #e8f5e8, stroke: #27ae60, stroke-width: 3px, color: #2c3e50, rx: 15, ry: 15, font-size: 14px
47 - classDef storage fill: #f3e8ff, stroke: #9b59b6, stroke-width: 3px, color: #2c3e50, rx: 15, ry: 15, font-size: 14px
48 - classDef output fill: #ffe8e8, stroke: #e74c3c, stroke-width: 3px, color: #2c3e50, rx: 15, ry: 15, font-size: 14px
49 - classDef userFeature fill: #fff2e8, stroke: #f39c12, stroke-width: 3px, color: #2c3e50, rx: 15, ry: 15, font-size: 14px
50 - classDef cloudFeature fill: #f0f8ff, stroke: #87ceeb, stroke-width: 3px, color: #2c3e50, rx: 15, ry: 15, font-size: 14px
51 - class Start input
52 - class LocalAgent input
53 - class End input
54 - class Discover process
55 - class Collect process
56 - class Detect process
57 - class Learn process
58 - class Check process
59 - class Store storage
60 - class Stream output
61 - class Export output
62 - class Alerts output
63 - class Dashboard userFeature
64 - class AIAssistant userFeature
65 - class ExternalDash userFeature
66 - class Notifications userFeature
67 - class Query cloudFeature
68 - class Score cloudFeature
69 - class MCP cloudFeature
70 - class Visualize cloudFeature
71 -```
72 -
73 -</details><br/>
74 -
75 -1. **Discover**: You can auto-detect metric sources on localhost and auto-discover metric sources on Kubernetes.
76 -2. **Collect**: Query data sources to collect metric samples, using the optimal protocol for each data source. You get 800+ integrations supported, including dozens of native application protocols, OpenMetrics and StatsD.
77 -3. **Detect Anomalies**: Use the trained machine learning models for each metric to detect in real-time if each sample collected is an outlier (an anomaly), or not.
78 -4. **Store**: Keep collected samples and their anomaly status, in the time-series database (database mode `dbengine`) or a ring buffer (database modes `ram` and `alloc`).
79 -5. **Learn**: Train multiple machine learning models for each metric collected, learning behaviors and patterns for detecting anomalies.
80 -6. **Check**: A health engine, triggering alerts and sending notifications. Netdata comes with hundreds of alert configurations that are automatically attached to metrics when they get collected, detecting errors, common configuration errors and performance issues.
81 -7. **Query**: A query engine for querying time-series data.
82 -8. **Score**: A scoring engine for comparing and correlating metrics.
83 -9. **Stream**: A mechanism to connect Netdata Agents and build Metrics Centralization Points (Netdata Parents).
84 -10. **Visualize**: Netdata's fully automated dashboards for all metrics.
85 -11. **Export**: Export metric samples to third party time-series databases, enabling you to use third party tools for visualization, like Grafana.
86 -
87 -## Comparison to Other Observability Solutions
88 -
89 -| Aspect | Traditional Solutions | Netdata |
90 -|---------------------------|----------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
91 -| **Architecture** | Multiple components (metrics exporters, time-series databases, visualization engines) requiring separate maintenance | One integrated package with everything included, even for Metrics Centralization Points |
92 -| **Setup & Configuration** | Manual configuration and setup required | Fully automated with comprehensive dashboards and alerts available instantly with zero configuration |
93 -| **Monitoring Fidelity** | Variable granularity depending on configuration | Console-level granularity and fidelity, plus holistic monitoring tools like [Top Monitoring](/docs/top-monitoring-netdata-functions.md) |
94 -| **System Impact** | Higher CPU usage, RAM utilization, and execution time impact on monitored systems | Minimal impact on monitored systems and applications, verified by [independent studies](https://www.ivanomalavolta.com/files/papers/ICSOC_2023.pdf) |
95 -| **Energy Efficiency** | Higher energy consumption | [Most energy efficient monitoring tool](https://twitter.com/IMalavolta/status/1734208439096676680) according to University of Amsterdam research |
96 -
97 -## Dashboard Versions
98 -
99 -Your Netdata Agents (Standalone, Children and Parents) **share the dashboard** of Netdata Cloud. However, when you are logged in and your Agent is connected to the Cloud, the following are enabled (which are otherwise disabled):
100 -
101 -1. **Access to Sensitive Data**: Some data, like systemd-journal logs and several [Top Monitoring](/docs/top-monitoring-netdata-functions.md) features expose sensitive data, like IPs, ports, process command lines and more. To access all these when the dashboard is served directly from an Agent, Netdata Cloud is required to verify that you have the required permissions to access the dashboard.
102 -
103 -2. **Dynamic Configuration**: You can configure Netdata Agents via configuration files, manually or through some provisioning system. The latest Netdata includes a feature to allow you to change some configurations (collectors, alerts) via the dashboard. This feature is only available to you if you have a paid Netdata Cloud plan.