b2c31a2ff · cryptotaxi247/netdata-1

@@ -24,842 +24,457 @@

24 <a href="https://scan.coverity.com/projects/netdata-netdata?tab=overview"><img alt="Coverity Scan" src="https://img.shields.io/coverity/scan/netdata"></a>

25

26

27 -Visit the <a href="https://www.netdata.cloud">Project's Home Page</a>

27 +

28 + <a href="https://registry.my-netdata.io/#menu_netdata_submenu_registry"><img src="https://registry.my-netdata.io/api/v3/badge.svg?chart=netdata.registry_entries&dimensions=persons&label=user%20base&units=M&value_color=blue&precision=2&divide=1000000&options=unaligned&tier=1&v44" alt="User base"></a>

29 + <a href="https://registry.my-netdata.io/#menu_netdata_submenu_registry"><img src="https://registry.my-netdata.io/api/v3/badge.svg?chart=netdata.registry_entries&dimensions=machines&label=servers%20monitored&units=M&divide=1000000&value_color=orange&precision=2&options=unaligned&tier=1&v44" alt="Servers monitored"></a>

30 + <a href="https://registry.my-netdata.io/#menu_netdata_submenu_registry"><img src="https://registry.my-netdata.io/api/v3/badge.svg?chart=netdata.registry_sessions&label=sessions%20served&units=M&value_color=yellowgreen&precision=2&divide=1000000&options=unaligned&tier=1&v44" alt="Sessions served"></a>

31 + <a href="https://hub.docker.com/r/netdata/netdata"><img src="https://registry.my-netdata.io/api/v3/badge.svg?chart=dockerhub.pulls_sum&divide=1000000&precision=1&units=M&label=docker+hub+pulls&options=unaligned&tier=1&v44" alt="Docker Hub pulls"></a>

32 +

33 +Visit our <a href="https://www.netdata.cloud">Home Page</a>

34

35 <hr class="solid">

36

38

33 -> **Important** :bulb:

34 -> People get addicted to Netdata. Once you use it on your systems, **there's no going back!**

39 +> [!WARNING]

40 +> People **get addicted to Netdata.**

41 +> Once you use it on your systems, **there's no going back!**

42

43 [![Platforms](https://img.shields.io/badge/Platforms-Linux%20%7C%20macOS%20%7C%20FreeBSD%20%7C%20Windows-blue)]()

44

38 -**TL;DR**

45 +## Most Energy-Efficient Monitoring Tool

46

40 -Netdata is an open-source, real-time infrastructure monitoring platform designed for instant visibility and proactive troubleshooting across your entire IT environment. It captures every metric, every second, providing detailed insights into systems, containers, applications, and logs without compromising performance or requiring complex setup.

47 +

48 +<img src="https://github.com/netdata/netdata/assets/139226121/4f64cbb6-05e4-48e3-b7c0-d1b79e37e219" alt="Energy efficiency" width="800"/>

49 +

50

42 -Key Advantages:

51 +According to the [University of Amsterdam study](https://www.ivanomalavolta.com/files/papers/ICSOC_2023.pdf), Netdata is "the most energy-efficient tool" for monitoring Docker-based systems. The study also shows Netdata excels in CPU usage, RAM usage, and execution time compared to other monitoring solutions.

52

44 -- **Instant Insights** Real-time, per-second metrics and visualizations for rapid problem detection.

45 -- **Automated and Zero-Configuration** Easy deployment with immediate monitoring—no complex setup needed.

46 -- **ML-Driven Intelligence** Built-in machine learning automatically detects anomalies, predicts issues, and assists in root-cause analysis.

47 -- **Highly Efficient** Proven minimal resource usage, exceptional scalability, and best-in-class energy efficiency validated by independent research.

48 -- **Distributed & Secure** Data stays securely within your infrastructure; no centralization required.

53 +---

54

50 -Netdata complements or replaces traditional monitoring tools, offering significant performance and usability advantages over Prometheus, Datadog, Dynatrace, and similar products, while remaining fully compatible and integration-friendly.

55 +## WHO WE ARE

56

52 -Designed for organizations seeking simplified operations, reduced overhead, and cost-effective monitoring solutions, Netdata provides a comprehensive, scalable, and user-friendly approach to observability.

57 +Netdata is an open-source, real-time infrastructure monitoring platform. Monitor, detect, and act across your entire infrastructure.

58

54 -**:sparkles: Key Features**:

59 +**Core Advantages:**

60

56 -- **Real-Time**

61 +* **Instant Insights** – With Netdata you can access per-second metrics and visualizations.

62 +* **Zero Configuration** – You can deploy immediately without complex setup.

63 +* **ML-Powered** – You can detect anomalies, predict issues, and automate analysis.

64 +* **Efficient** – You can monitor with minimal resource usage and maximum scalability.

65 +* **Secure & Distributed** – You can keep your data local with no central collection needed.

66

58 - Per-second data collection and real-time processing provides immediate visibility into your infrastructure's behavior.

67 +With Netdata, you get real-time, per-second updates. Clear **insights at a glance**, no complexity.

68

60 - _**Unique**: Netdata works in a beat, and everything happens at this pace. You hit Enter in the terminal, and just a second later, the result appears on the dashboard._

69 +---

70

62 -- **Zero-Configuration**

71 +## Key Features

72

64 - Start monitoring in minutes with automatic detection and discovery, fully automated dashboards, and hundreds of pre-configured alerts.

73 +| Feature | Description | What Makes It Unique |

74 +|----------------------------|-------------------------------------------|----------------------------------------------------------|

75 +| **Real-Time** | Per-second data collection and processing | Works in a beat – click and see results instantly |

76 +| **Zero-Configuration** | Automatic detection and discovery | Auto-discovers everything on the nodes it runs |

77 +| **ML-Powered** | Unsupervised anomaly detection | Trains multiple ML models per metric at the edge |

78 +| **Long-Term Retention** | High-performance storage | ~0.5 bytes per sample with tiered storage for archiving |

79 +| **Advanced Visualization** | Rich, interactive dashboards | Slice and dice data without query language |

80 +| **Extreme Scalability** | Native horizontal scaling | Parent-Child centralization with multi-million samples/s |

81 +| **Complete Visibility** | From infrastructure to applications | Simplifies operations and eliminates silos |

82 +| **Edge-Based** | Processing at your premises | Distributes code instead of centralizing data |

83

66 - _**Unique**: Netdata auto-discovers everything on the nodes it runs. All kernel technologies, all processes, all applications, all containers, all hardware components. And with its dynamic configuration, any changes can be done via the dashboard._

84 +> [!NOTE]

85 +> Want to put Netdata to the test against Prometheus?

86 +> Explore the [full comparison](https://www.netdata.cloud/blog/netdata-vs-prometheus-2025/).

87

68 -- **ML-Powered**

88 +---

89

70 - Unsupervised anomaly detection and pattern recognition for all metrics, providing advanced correlations and instant root cause analysis.

90 +## Netdata Ecosystem

91

72 - _**Unique**: Netdata trains multiple true ML models per metric, at the edge, for all metrics!_

73 - _**Unique**: A scoring engine identifies correlations across metrics, applications, nodes, services, even cloud providers and data centers!_

74 -

75 -- **Long-Term Retention**

92 +This three-part architecture enables you to scale from single nodes to complex multi-cloud environments:

93

77 - High-performance and efficient tiered storage for years of retention and fast query responses.

94 +| Component | Description | License |

95 +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|

96 +| **Netdata Agent** | • Core monitoring engine • Handles collection, storage, ML, alerts, exports • Runs on servers, cloud, K8s, IoT • Zero production impact | [GPL v3+](https://www.gnu.org/licenses/gpl-3.0) |

97 +| **Netdata Cloud** | • Enterprise features • User management, RBAC, horizontal scaling • Centralized alerts • Free community tier • No metric storage centralization | |

98 +| **Netdata UI** | • Dashboards and visualizations • Free to use • Included in standard packages • Latest version via CDN | [NCUL1](https://app.netdata.cloud/LICENSE.txt) |

99

79 - _**Unique**: Netdata needs ~0.5 per sample on disk, offering superb compression for high-resolution data!_

80 - _**Unique**: A tiered storage engine automatically downsamples old data for archiving, long term retention and capacity planning._

100 +## What You Can Monitor

101

82 -- **Advanced Visualization**

102 +With Netdata you can monitor all these components across platforms:

103

84 - Rich, interactive low-latency dashboards for deep system and applications insights and rapid troubleshooting.

105 +|------------------------------------------------------------------------------------------------------------:|:--------------------------------:|:-------:|:-----:|:-------------------------------------------------:|

106 +| **System Resources** CPU, Memory and system shared resources | Full | Yes | Yes | Yes |

107 +| **Storage** Disks, Mount points, Filesystems, RAID arrays | Full | Yes | Yes | Yes |

108 +| **Network** Network Interfaces, Protocols, Firewall, etc | Full | Yes | Yes | Yes |

110 +| **O/S Services** Resources, Performance and Status | Yes `systemd` | - | - | - |

111 +| **Processes** Resources, Performance, OOM, and more | Yes | Yes | Yes | Yes |

112 +| System and Application **Logs** | Yes `systemd`-journal | - | - | Yes `Windows Event Log`, `ETW` |

113 +| **Network Connections** Live TCP and UDP sockets per PID | Yes | - | - | - |

114 +| **Containers** Docker/containerd, LXC/LXD, Kubernetes, etc | Yes | - | - | - |

115 +| **VMs** (from the host) KVM, qemu, libvirt, Proxmox, etc | Yes `cgroups` | - | - | Yes `Hyper-V` |

116 +| **Synthetic Checks** Test APIs, TCP ports, Ping, Certificates, etc | Yes | Yes | Yes | Yes |

117 +| **Packaged Applications** nginx, apache, postgres, redis, mongodb, and hundreds more | Yes | Yes | Yes | Yes |

118 +| **Cloud Provider Infrastructure** AWS, GCP, Azure, and more | Yes | Yes | Yes | Yes |

119 +| **Custom Applications** OpenMetrics, StatsD and soon OpenTelemetry | Yes | Yes | Yes | Yes |

120

86 - _**Unique**: Netdata dashboards allow you to slice and dice any dataset, without learning a query language._

87 - _**Unique**: A multi-faceted query engine, analyzes all aspects of your data in one go, and the dashboard provides interactive analysis for all them (NIDL framework)._

88 -

89 -- **Extreme Scalability**

121 +On Linux, you can continuously monitor all kernel features and hardware sensors for errors, including Intel/AMD/Nvidia GPUs, PCI AER, RAM EDAC, IPMI, S.M.A.R.T, Intel RAPL, NVMe, fans, power supplies, and voltage readings.

122

91 - Native horizontal scalability, while maintaining performance and ease of use.

123 +---

124

93 - _**Unique**: Simple Parent-Child centralization and native horizontal scalability._

94 - _**Unique**: Each Netdata can scale to multi-million samples/s with best in-class resources utilization._

95 -

96 -- **Complete End-to-End Visibility**

125 +## Getting Started

126

98 - From infrastructure to applications, logs to metrics, hardware to databases, all in one solution.

127 +You can install Netdata on all major operating systems. To begin:

128

100 - _**Unique**: Netdata is built to simplify your operations, empower your team, provide clarity and eliminate silos._

101 -

102 -- **Edge-Based**

129 +### 1. Install Netdata

130

104 - All processing and storage of your data, at your premises, as close to the edge as possible.

131 +Choose your platform and follow the installation guide:

132

106 - _**Unique**: Instead of centralizing observability data, Netdata distributes the code. This provides higher processing capacity by utilizing resources that are usually available and spare, while eliminating most of the cost involved for metrics and logs management._

133 +* [Linux Installation](https://learn.netdata.cloud/docs/installing/one-line-installer-for-all-linux-systems)

134 +* [macOS](https://learn.netdata.cloud/docs/installing/macos)

135 +* [FreeBSD](https://learn.netdata.cloud/docs/installing/freebsd)

136 +* [Windows](https://learn.netdata.cloud/docs/netdata-agent/installation/windows)

137 +* [Docker Guide](/packaging/docker/README.md)

138 +* [Kubernetes Setup](https://learn.netdata.cloud/docs/installation/install-on-specific-environments/kubernetes)

139

108 ----

140 +> [!NOTE]

141 +> You can access the Netdata UI at `http://localhost:19999` (or `http://NODE:19999` if remote).

142

110 -### The Netdata Ecosystem

111 -

112 -> **Note**: This repository contains the Netdata Agent, the open-source core of the Netdata ecosystem. For information about other components, see below.

113 -

114 -This three-part architecture enables Netdata to scale seamlessly from single-node deployments to complex multi-cloud environments with thousands of nodes, supporting long-term data retention without compromising performance.

115 -

116 -| Component | Description | License |

117 -|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|

118 -| Netdata Agent | • The heart of Netdata's monitoring capabilities • Handles data collection, storage, querying, ML analysis, exports, and alerts • Runs on physical/virtual servers, cloud, Kubernetes, and IoT devices • Optimized for zero production impact • Core of all observability features | [GPL v3+](https://www.gnu.org/licenses/gpl-3.0) |

119 -| Netdata Cloud | • Adds enterprise-grade features  (user management and RBAC, horizontal scalability,   centralized alert management, access from anywhere) • Available as SaaS or on-premises • Includes free community tier • Does not centralize metric storage | |

120 -| Netdata UI | • Powers all dashboards and visualizations • Free to use with both Agent and Cloud • Included in standard Netdata packages • Latest version available via CDN | [NCUL1](https://app.netdata.cloud/LICENSE.txt) |

121 -

122 -### Key capabilities of the Netdata Agent

123 -

124 -With these capabilities, Netdata Agent provides a powerful, automated monitoring solution that works right out-of-the-box while remaining highly customizable for specific needs.

125 -

126 -| Capability | Description |

127 -|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

128 -| Comprehensive Data Collection | • 800+ integrations out of the box • Collects metrics from systems, containers, VMs, hardware sensors • Supports OpenMetrics exporters, StatsD, and logs • OpenTelemetry support coming soon |

129 -| Performance & Precision | • Per-second data collection • Real-time visualization with 1-second latency • High-resolution metrics for precise monitoring |

130 -| Edge-Based ML | • Trains ML models directly at the edge • Automatic anomaly detection per metric • Pattern recognition based on historical behavior |

131 -| Advanced Log Management | • Direct systemd-journald and Windows Event Log integrations • Tools for log conversion (log2journal, systemd-cat-native) • Process logs at the edge - no centralization needed • Rich log visualization dashboards |

132 -| Observability Pipeline | • Build Parent-Child relationships between Agents • Create flexible centralization points • Control data replication and retention at multiple levels |

133 -| Automated Visualization | • NIDL (Nodes, Instances, Dimensions & Labels) data model • Auto-generated, correlated dashboards • Filter and analyze data without query language • Free to use, powered by Netdata UI |

134 -| Smart Alerting | • Hundreds of pre-configured alerts • Detect common issues automatically • Multiple notification methods • Proactive problem detection |

135 -| Low Maintenance | • Auto-detection of metrics • Zero-touch machine learning • Easy scalability • CI/CD friendly deployment |

136 -| Open & Extensible | • Modular architecture • Easy to extend and customize • Integrates with existing monitoring tools • Active community ecosystem |

137 -

138 -### What can be monitored with the Netdata Agent

139 -

140 -Netdata monitors all the following:

141 -

143 -|------------------------------------------------------------------------------------------------------------:|:--------------------------------:|:-------:|:-----:|:-------------------------------------------------------------------------------:|

144 -| **System Resources** CPU, Memory and system shared resources | Full | Yes | Yes | Yes |

145 -| **Storage** Disks, Mount points, Filesystems, RAID arrays | Full | Yes | Yes | Yes |

146 -| **Network** Network Interfaces, Protocols, Firewall, etc | Full | Yes | Yes | Yes |

148 -| **O/S Services** Resources, Performance and Status | Yes `systemd` | - | - | - |

149 -| **Processes** Resources, Performance, OOM, and more | Yes | Yes | Yes | Yes |

150 -| System and Application **Logs** | Yes `systemd`-journal | - | - | Yes `Windows Event Log`, and `Event Tracing for Windows` |

151 -| **Network Connections** Live TCP and UDP sockets per PID | Yes | - | - | - |

152 -| **Containers** Docker/containerd, LXC/LXD, Kubernetes, etc | Yes | - | - | - |

153 -| **VMs** (from the host) KVM, qemu, libvirt, Proxmox, etc | Yes `cgroups` | - | - | Yes `Hyper-V` |

154 -| **Synthetic Checks** Test APIs, TCP ports, Ping, Certificates, etc | Yes | Yes | Yes | Yes |

155 -| **Packaged Applications** nginx, apache, postgres, redis, mongodb, and hundreds more | Yes | Yes | Yes | Yes |

156 -| **Cloud Provider Infrastructure** AWS, GCP, Azure, and more | Yes | Yes | Yes | Yes |

157 -| **Custom Applications** OpenMetrics, StatsD and soon OpenTelemetry | Yes | Yes | Yes | Yes |

158 -

159 -When operating on Linux, the Netdata Agent continuously monitors every available kernel feature and all hardware sensors for errors. This covers Intel, AMD, and Nvidia GPUs, PCI Advanced Error Reporting (PCI AER), RAM Error Detection and Correction (RAM EDAC), Intelligent Platform Management Interface (IPMI), S.M.A.R.T. for disks, Intel Running Average Power Limit (Intel RAPL), NVMe disks, as well as fans, power supplies, voltage readings, and more.

143 +### 2. Configure Collectors

144

161 ----

145 +Netdata auto-discovers most metrics, but you can manually configure some collectors:

146

163 -### :star: Netdata is the most energy-efficient monitoring tool :star:

147 +* [All collectors](https://learn.netdata.cloud/docs/data-collection/)

148 +* [SNMP monitoring](https://learn.netdata.cloud/docs/data-collection/monitor-anything/networking/snmp)

149

165 -

166 -<a href="https://www.ivanomalavolta.com/files/papers/ICSOC_2023.pdf#gh-dark-mode-only">

167 - <img src="https://github.com/netdata/netdata/assets/139226121/7118757a-38fb-48d7-b12a-53e709a8e8c0" alt="Energy Efficiency" width="1000"/>

168 -</a>

169 -<a href="https://www.ivanomalavolta.com/files/papers/ICSOC_2023.pdf#gh-light-mode-only">

170 - <img src="https://github.com/netdata/netdata/assets/139226121/4f64cbb6-05e4-48e3-b7c0-d1b79e37e219" alt="Energy efficiency" width="1000"/>

171 -</a>

172 -

150 +### 3. Configure Alerts

151

174 -Dec 11, 2023: [University of Amsterdam published a study](https://twitter.com/IMalavolta/status/1734208439096676680) related to the impact of monitoring tools for Docker based systems, aiming to answer 2 questions:

152 +You can use hundreds of built-in alerts and integrate with:

153

176 -1. **The impact of monitoring on the energy efficiency of Docker-based systems**

177 -2. **The impact of monitoring on Docker-based systems?**

154 +`email`, `Slack`, `Telegram`, `PagerDuty`, `Discord`, `Microsoft Teams`, and more.

155

179 -- 🚀 Netdata excels in energy efficiency: **"... Netdata is the most energy-efficient tool ..."**, as the study says.

180 -- 🚀 Netdata excels in CPU Usage, RAM Usage and Execution Time, and has a similar impact on Network Traffic as Prometheus.

156 +> [!NOTE]

157 +> Email alerts work by default if there's a configured MTA.

158

182 -The study didn’t normalize the results based on the number of metrics collected. Given that Netdata usually collects significantly more metrics than the other tools, Netdata managed to outperform the other tools, while ingesting a much higher number of metrics. [Read the full study here](https://www.ivanomalavolta.com/files/papers/ICSOC_2023.pdf).

159 +### 4. Configure Parents

160

184 ----

161 +You can centralize dashboards, alerts, and storage with Netdata Parents:

162

186 -### Netdata vs Prometheus 2025 Review

163 +* [Streaming Reference](https://learn.netdata.cloud/docs/streaming/streaming-configuration-reference)

164

188 -

189 -<a href="https://blog.netdata.cloud/netdata-vs-prometheus-performance-analysis#gh-light-mode-only">

190 - <img src="https://github.com/netdata/netdata/assets/139226121/6c21ae39-8656-45c3-bc85-4b012679d2bb" alt="Netdata" width="1000"/>

191 -</a>

192 -<a href="https://blog.netdata.cloud/netdata-vs-prometheus-performance-analysis#gh-dark-mode-only">

193 - <img src="https://github.com/netdata/netdata/assets/139226121/f2dbde46-d3dd-4807-bd34-966da4d0ec22" alt="Netdata" width="1000"/>

194 -</a>

195 -

165 +> [!NOTE]

166 +> You can use Netdata Parents for central dashboards, longer retention, and alert configuration.

167

197 -NEW! On the same workload, Netdata uses **1/3rd less CPU**, consumes **1/8th of the RAM**, performes **31 times less disk I/O** and stores **40 times more data** while being up to **22 times faster** in query responses! [Read the full 2025 review in our blog](https://www.netdata.cloud/blog/netdata-vs-prometheus-2025/).

168 +### 5. Connect to Netdata Cloud

169

199 ----

170 +[Sign in to Netdata Cloud](https://app.netdata.cloud/sign-in) and connect your nodes for:

171

201 -

202 -

203 - <img src="https://raw.githubusercontent.com/cncf/artwork/master/other/cncf/horizontal/white/cncf-white.svg#gh-dark-mode-only" alt="CNCF" width="300">

204 - <img src="https://raw.githubusercontent.com/cncf/artwork/master/other/cncf/horizontal/black/cncf-black.svg#gh-light-mode-only" alt="CNCF" width="300">

205 -

206 - Netdata actively supports and is a member of the Cloud Native Computing Foundation (CNCF)

207 -

208 - ...and due to your love :heart:, it is one of the most :star:'d projects in the <a href="https://landscape.cncf.io/?item=observability-and-analysis--observability--netdata">CNCF landscape</a>!

209 -

210 -

172 +* Access from anywhere

173 +* Horizontal scalability and multi-node dashboards

174 +* UI configuration for alerts and data collection

175 +* Role-based access control

176 +* Free tier available

177

212 -<hr class="solid">

178 +> [!NOTE]

179 +> Netdata Cloud is optional. Your data stays in your infrastructure.

180 +

181 +## Live Demo Sites

182

183

215 - You can see Netdata live!

216 - <a href="https://frankfurt.netdata.rocks">FRANKFURT</a> |

217 - <a href="https://newyork.netdata.rocks">NEWYORK</a> |

218 - <a href="https://atlanta.netdata.rocks">ATLANTA</a> |

219 - <a href="https://sanfrancisco.netdata.rocks">SANFRANCISCO</a> |

220 - <a href="https://toronto.netdata.rocks">TORONTO</a> |

221 - <a href="https://singapore.netdata.rocks">SINGAPORE</a> |

222 - <a href="https://bangalore.netdata.rocks">BANGALORE</a>

184 + See Netdata in action

185 + <a href="https://frankfurt.netdata.rocks">FRANKFURT</a> |

186 + <a href="https://newyork.netdata.rocks">NEWYORK</a> |

187 + <a href="https://atlanta.netdata.rocks">ATLANTA</a> |

188 + <a href="https://sanfrancisco.netdata.rocks">SANFRANCISCO</a> |

189 + <a href="https://toronto.netdata.rocks">TORONTO</a> |

190 + <a href="https://singapore.netdata.rocks">SINGAPORE</a> |

191 + <a href="https://bangalore.netdata.rocks">BANGALORE</a>

192

224 - We've set up multiple demo clusters around the world, each running with the default configuration and showing real monitoring data.

193 + These demo clusters run with default configuration and show real monitoring data.

194

226 - Choose the instance closest to you for the best experience.

195 + Choose the instance closest to you for the best performance.

196

197

229 -<hr class="solid">

198 +---

199

231 -## Getting Started

200 +## How It Works

201 +

202 +With Netdata you can run a modular pipeline for metrics collection, processing, and visualization.

203 +

204 +```mermaid

205 +flowchart TB

206 + A[Netdata Agent]

207 + A1(Collect):::green --> A

208 + A2(Store):::green --> A

209 + A3(Learn):::green --> A

210 + A4(Detect):::green --> A

211 + A5(Check):::green --> A

212 + A6(Stream):::green --> A

213 + A7(Archive):::green --> A

214 + A8(Query):::green --> A

215 + A9(Score):::green --> A

216 +

217 + classDef green fill:#bbf3bb,stroke:#333,stroke-width:1px

218 + ```

219 +

220 +With each Agent you can:

221 +

222 +1. **Collect** – Gather metrics from systems, containers, apps, logs, APIs, and synthetic checks.

223 +2. **Store** – Save metrics to a high-efficiency, tiered time-series database.

224 +3. **Learn** – Train ML models per metric using recent behavior.

225 +4. **Detect** – Identify anomalies using trained ML models.

226 +5. **Check** – Evaluate metrics against pre-set or custom alert rules.

227 +6. **Stream** – Send metrics to Netdata Parents in real time.

228 +7. **Archive** – Export metrics to Prometheus, InfluxDB, OpenTSDB, Graphite, and others.

229 +8. **Query** – Access metrics via an API for dashboards or third-party tools.

230 +9. **Score** – Use a scoring engine to find patterns and correlations across metrics.

231 +

232 +> [!NOTE]

233 +> Learn more: [Netdata's architecture](https://learn.netdata.cloud/docs/netdata-agent/architecture-overview/)

234 +

235 +## Agent Capabilities

236 +

237 +With the Netdata Agent, you can use these core capabilities out-of-the-box:

238 +

239 +| Capability | Description |

240 +|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|

241 +| **Comprehensive Collection** | • 800+ integrations • Systems, containers, VMs, hardware sensors • OpenMetrics, StatsD, and logs • OpenTelemetry support coming soon |

242 +| **Performance & Precision** | • Per-second collection • Real-time visualization with 1-second latency • High-resolution metrics |

243 +| **Edge-Based ML** | • ML models trained at the edge • Automatic anomaly detection per metric • Pattern recognition based on historical behavior |

244 +| **Advanced Log Management** | • Direct systemd-journald and Windows Event Log integration • Process logs at the edge • Rich log visualization |

245 +| **Observability Pipeline** | • Parent-Child relationships • Flexible centralization • Multi-level replication and retention |

246 +| **Automated Visualization** | • NIDL data model • Auto-generated dashboards • No query language needed |

247 +| **Smart Alerting** | • Pre-configured alerts • Multiple notification methods • Proactive detection |

248 +| **Low Maintenance** | • Auto-detection • Zero-touch ML • Easy scalability • CI/CD friendly |

249 +| **Open & Extensible** | • Modular architecture • Easy to customize • Integrates with existing tools |

250 +

251 +---

252 +

253 +## CNCF Membership

254

255

234 - <a href="https://registry.my-netdata.io/#menu_netdata_submenu_registry"><img src="https://registry.my-netdata.io/api/v3/badge.svg?chart=netdata.registry_entries&dimensions=persons&label=user%20base&units=M&value_color=blue&precision=2&divide=1000000&options=unaligned&tier=1&v44" alt="User base"></a>

235 - <a href="https://registry.my-netdata.io/#menu_netdata_submenu_registry"><img src="https://registry.my-netdata.io/api/v3/badge.svg?chart=netdata.registry_entries&dimensions=machines&label=servers%20monitored&units=M&divide=1000000&value_color=orange&precision=2&options=unaligned&tier=1&v44" alt="Servers monitored"></a>

236 - <a href="https://registry.my-netdata.io/#menu_netdata_submenu_registry"><img src="https://registry.my-netdata.io/api/v3/badge.svg?chart=netdata.registry_sessions&label=sessions%20served&units=M&value_color=yellowgreen&precision=2&divide=1000000&options=unaligned&tier=1&v44" alt="Sessions served"></a>

237 - <a href="https://hub.docker.com/r/netdata/netdata"><img src="https://registry.my-netdata.io/api/v3/badge.svg?chart=dockerhub.pulls_sum&divide=1000000&precision=1&units=M&label=docker+hub+pulls&options=unaligned&tier=1&v44" alt="Docker Hub pulls"></a>

256 + <img src="https://raw.githubusercontent.com/cncf/artwork/master/other/cncf/horizontal/black/cncf-black.svg" alt="CNCF" width="300">

257

239 - <a href="https://registry.my-netdata.io/#menu_netdata_submenu_registry"><img src="https://registry.my-netdata.io/api/v3/badge.svg?chart=netdata.registry_entries&dimensions=persons&after=-86400&options=unaligned&group=incremental-sum&label=new%20users%20today&units=null&value_color=blue&precision=0&options=unaligned&tier=1&v44" alt="New users today"></a>

240 - <a href="https://registry.my-netdata.io/#menu_netdata_submenu_registry"><img src="https://registry.my-netdata.io/api/v3/badge.svg?chart=netdata.registry_entries&dimensions=machines&group=incremental-sum&after=-86400&options=unaligned&label=servers%20added%20today&units=null&value_color=orange&precision=0&tier=1&v44" alt="New machines today"></a>

241 - <a href="https://registry.my-netdata.io/#menu_netdata_submenu_registry"><img src="https://registry.my-netdata.io/api/v3/badge.svg?chart=netdata.registry_sessions&after=-86400&group=incremental-sum&options=unaligned&label=sessions%20served%20today&units=null&value_color=yellowgreen&precision=0&tier=1&v44" alt="Sessions today"></a>

242 - <a href="https://hub.docker.com/r/netdata/netdata"><img src="https://registry.my-netdata.io/api/v3/badge.svg?chart=dockerhub.pulls_sum&divide=1000&precision=1&units=k&label=docker+hub+pulls&after=-86400&group=incremental-sum&label=docker%20hub%20pulls%20today&options=unaligned&tier=1&v44" alt="Docker Hub pulls today"></a>

258 + Netdata actively supports and is a member of the Cloud Native Computing Foundation (CNCF).

259 + It is one of the most starred projects in the <a href="https://landscape.cncf.io/?item=observability-and-analysis--observability--netdata">CNCF landscape</a>.

260

261

245 -### 1. **Install Netdata everywhere** :v:

246 -

247 -Netdata can be installed on all Linux, macOS, FreeBSD and Windows systems. We provide binary packages for the most popular operating systems and package managers.

248 -

249 -- Install on [Ubuntu, Debian CentOS, Fedora, Suse, Red Hat, Arch, Alpine, Gentoo, even BusyBox](https://learn.netdata.cloud/docs/installing/one-line-installer-for-all-linux-systems).

250 -- Install with [Docker](/packaging/docker/README.md).

251 - Netdata is a [Verified Publisher on DockerHub](https://hub.docker.com/r/netdata/netdata) and our users enjoy free unlimited DockerHub pulls :heart_eyes:.

252 -- Install on [macOS](https://learn.netdata.cloud/docs/installing/macos) :metal:.

253 -- Install on [FreeBSD](https://learn.netdata.cloud/docs/installing/freebsd) and [pfSense](https://learn.netdata.cloud/docs/installing/pfsense).

254 -- Install on [Windows](https://learn.netdata.cloud/docs/netdata-agent/installation/windows).

255 -- Install [from source](https://learn.netdata.cloud/docs/installing/build-the-netdata-agent-yourself/compile-from-source-code) ![github downloads](https://img.shields.io/github/downloads/netdata/netdata/total?color=success&logo=github)

256 -- For Kubernetes deployments [check here](https://learn.netdata.cloud/docs/installation/install-on-specific-environments/kubernetes/).

257 -

258 -Check also the [Netdata Deployment Guides](https://learn.netdata.cloud/docs/deployment-guides/) to decide how to deploy it in your infrastructure.

259 -

260 -By default, you will have immediately available a local dashboard. Netdata starts a web server for its dashboard at port `19999`. Open up your web browser of choice and

261 -navigate to `http://NODE:19999`, replacing `NODE` with the IP address or hostname of your Agent. If installed on localhost, you can access it through `http://localhost:19999`.

262 -

263 -_Note: the binary packages we provide, install Netdata UI automatically. Netdata UI is closed-source, but free to use with Netdata Agents and Netdata Cloud._

264 -

265 -### 2. **Configure Collectors** :boom:

266 -

267 -Netdata auto-detects and auto-discovers most operating system data sources and applications. However, many data sources require some manual configuration, usually to allow Netdata to get access to the metrics.

268 -

269 -- For a detailed list of the 800+ collectors available, check [this guide](https://learn.netdata.cloud/docs/data-collection/).

270 -- To monitor SNMP devices, check [this guide](https://learn.netdata.cloud/docs/data-collection/monitor-anything/networking/snmp).

271 -

272 -### 3. **Configure Alert Notifications** :bell:

273 -

274 -Netdata comes with hundreds of pre-configured alerts that automatically check your metrics immediately after they start getting collected.

275 -

276 -Netdata can dispatch alert notifications to multiple third party systems, including: `email`, `Alerta`, `AWS SNS`, `Discord`, `Dynatrace`, `flock`, `gotify`, `IRC`, `Matrix`, `MessageBird`, `Microsoft Teams`, `ntfy`, `OPSgenie`, `PagerDuty`, `Prowl`, `PushBullet`, `PushOver`, `RocketChat`, `Slack`, `SMS tools`, `Syslog`, `Telegram`, `Twilio`.

277 -

278 -By default, Netdata will send e-mail notifications if there is a configured MTA on the system.

279 -

280 -### 4. **Configure Netdata Parents** :family:

281 -

282 -Optionally, configure one or more Netdata Parents. A Netdata Parent is a Netdata Agent that has been configured to accept [streaming connections](https://learn.netdata.cloud/docs/streaming/streaming-configuration-reference) from other Netdata Agents.

283 -

284 -Netdata Parents provide:

285 -

286 -- **Infrastructure level dashboards, at `http://parent.server.ip:19999/`.**

287 -

288 - Each Netdata Agent has an API listening at the TCP port 19999 of each server.

289 - When you hit that port with a web browser (e.g. `http://server.ip:19999/`), the Netdata Agent UI is presented.

290 - When the Netdata Agent is also a Parent, the UI of the Parent includes data for all nodes that stream metrics to that Parent.

291 -

292 -- **Increased retention for all metrics of all your nodes.**

293 -

294 - Each Netdata Agent maintains each own database of metrics. But Parents can be given additional resources to maintain a much longer database than

295 - individual Netdata Agents.

296 -

297 -- **Central configuration of alerts and dispatch of notifications.**

298 -

299 - Using Netdata Parents, all the alert notifications integrations can be configured only once at the Parent and they can be disabled at the Netdata Agents.

300 -

301 -You can also use Netdata Parents to:

302 -

303 -- Offload your production systems (the parents run ML, alerts, queries, etc. for all their children)

304 -- Secure your production systems (the parents accept user connections for all their children)

305 -

306 -### 5. **Connect to Netdata Cloud** :cloud:

307 -

308 -[Sign-in](https://app.netdata.cloud/sign-in) to [Netdata Cloud](https://www.netdata.cloud/) and connect your Netdata Agents and Parents.

309 -If you connect your Netdata Parents, there is no need to connect your Netdata Agents. They will be connected via the Parents.

310 -

311 -When your Netdata nodes are connected to Netdata Cloud, you can (on top of the above):

312 -

313 -- Access your Netdata Agents from anywhere

314 -- Access sensitive Netdata Agent features (like "Netdata Functions": processes, systemd-journal)

315 -- Organize your infra in spaces and Rooms

316 -- Create, manage, and share **custom dashboards**

317 -- Invite your team and assign roles to them (Role-Based Access Control)

318 -- Get infinite horizontal scalability (multiple independent Netdata Agents are viewed as one infra)

319 -- Configure alerts from the UI

320 -- Configure data collection from the UI

321 -- Netdata Mobile App notifications

322 -

323 -:love_you_gesture: Netdata Cloud doesn’t prevent you from using your Netdata Agents and Parents directly, and vice versa.

324 -

325 -:ok_hand: Your metrics are still stored in your network when you connect your Netdata Agents and Parents to Netdata Cloud.

326 -

327 -<hr class="solid">

328 -

329 -## How it works

330 -

331 -Netdata is built around a **modular metrics processing pipeline**.

332 -

333 -<details><summary>Click to see more details about this pipeline...</summary>

334 -

335 -

336 -Each Netdata Agent can perform the following functions:

337 -

338 -1. **`COLLECT` metrics from their sources**

339 - Uses [internal](https://github.com/netdata/netdata/tree/master/src/collectors) and [external](https://github.com/netdata/go.d.plugin/tree/master/modules) plugins to collect data from their sources.

340 -

341 - Netdata auto-detects and collects almost everything from the operating system: including CPU, Interrupts, Memory, Disks, Mount Points, Filesystems, Network Stack, Network Interfaces, Containers, VMs, Processes, `systemd` units, Linux Performance Metrics, Linux eBPF, Hardware Sensors, IPMI, and more.

342 -

343 - It collects application metrics from applications: PostgreSQL, MySQL/MariaDB, Redis, MongoDB, Nginx, Apache, and hundreds more.

344 -

345 - Netdata also collects your custom application metrics by scraping OpenMetrics exporters, or via StatsD.

346 -

347 - It can convert web server log files to metrics and apply ML and alerts to them in real-time.

348 -

349 - And it also supports synthetic tests / white box tests, so you can ping servers, check API responses, or even check filesystem files and directories to generate metrics, train ML and run alerts and notifications on their status.

350 -

351 -2. **`STORE` metrics to a database**

352 - Uses database engine plugins to store the collected data, either in memory and/or on disk. We have developed our own [`dbengine`](https://github.com/netdata/netdata/tree/master/src/database/engine#readme) for storing the data in a very efficient manner, allowing Netdata to have less than one byte per sample on disk and amazingly fast queries.

353 -

354 -3. **`LEARN` the behavior of metrics** (ML)

355 - Trains multiple Machine-Learning (ML) models per metric to learn the behavior of each metric individually. Netdata uses the `kmeans` algorithm and creates by default a model per metric per hour, based on the values collected for that metric over the last 6 hours. The trained models are persisted to disk.

356 -

357 -4. **`DETECT` anomalies in metrics** (ML)

358 - Uses the trained machine learning (ML) models to detect outliers and mark collected samples as **anomalies**. Netdata stores anomaly information together with each sample and also streams it to Netdata Parents so that the anomaly is also available at query time for the whole retention of each metric.

359 -

360 -5. **`CHECK` metrics and trigger alert notifications**

361 - Uses its configured alerts (you can configure your own) to check the metrics for common issues and uses notification plugins to send alert notifications.

362 -

363 -6. **`STREAM` metrics to other Netdata Agents**

364 - Push metrics in real-time to Netdata Parents.

365 -

366 -7. **`ARCHIVE` metrics to third party databases**

367 - Export metrics to industry standard time-series databases, like `Prometheus`, `InfluxDB`, `OpenTSDB`, `Graphite`, etc.

368 -

369 -8. **`QUERY` metrics and present dashboards**

370 - Provide an API to query the data and present interactive dashboards to users.

371 -

372 -9. **`SCORE` metrics to reveal similarities and patterns**

373 - Score the metrics according to the given criteria, to find the needle in the haystack.

374 -

375 -When using Netdata Parents, all the functions of a Netdata Agent (except data collection) can be delegated to Parents to offload production systems.

376 -

377 -The core of Netdata is developed in C. We have our own `libnetdata`, that provides:

378 -

379 -- **`DICTIONARY`**

380 - A high-performance algorithm to maintain both indexed and ordered pools of structures Netdata needs. It uses JudyHS arrays for indexing, although it is modular: any hashtable or tree can be integrated into it. Despite being in C, dictionaries follow object-oriented programming principles, so there are constructors, destructors, automatic memory management, garbage collection, and more. For more, see [here](https://github.com/netdata/netdata/tree/master/src/libnetdata/dictionary).

381 -

382 -- **`ARAL`**

383 - ARray ALlocator (ARAL) is used to minimize the system allocations made by Netdata. ARAL is optimized for maximum multithreaded performance. It also allows all structures that use it to be allocated in memory-mapped files (shared memory) instead of RAM. For more, see [here](https://github.com/netdata/netdata/tree/master/src/libnetdata/aral).

384 -

385 -- **`PROCFILE`**

386 - A high-performance `/proc` (but also any) file parser and text tokenizer. It achieves its performance by keeping files open and adjusting its buffers to read the entire file in one call (which is also required by the Linux kernel). For more, see [here](https://github.com/netdata/netdata/tree/master/src/libnetdata/procfile).

387 -

388 -- **`STRING`**

389 - A string internet mechanism, for string deduplication and indexing (using JudyHS arrays), optimized for multithreaded usage. For more, see [here](https://github.com/netdata/netdata/tree/master/src/libnetdata/string).

390 -

391 -- **`ARL`**

392 - Adaptive Resortable List (ARL) is a very fast list iterator, that keeps the expected items on the list in the same order they are found in an input list. So, the first iteration is somewhat slower, but all the following iterations are perfectly aligned for the best performance. For more, see [here](https://github.com/netdata/netdata/tree/master/src/libnetdata/adaptive_resortable_list).

393 -

394 -- **`BUFFER`**

395 - A flexible text buffer management system that allows Netdata to automatically handle dynamically sized text buffer allocations. The same mechanism is used for generating consistent JSON output by the Netdata APIs. For more, see [here](https://github.com/netdata/netdata/tree/master/src/libnetdata/buffer).

396 -

397 -- **`SPINLOCK`**

398 - Like POSIX `MUTEX` and `RWLOCK` but a lot faster, based on atomic operations, with significantly smaller memory impact, while being portable.

399 -

400 -- **`PGC`**

401 - A caching layer that can be used to cache any kind of time-related data, with automatic indexing (based on a tree of JudyL arrays), memory management, evictions, flushing, pressure management. This is extensively used in `dbengine`. For more, see [here](/src/database/engine/README.md).

402 -

403 -The above, and many more, allow Netdata developers to work on the application fast and with confidence. Most of the business logic in Netdata is a work of mixing the above.

404 -

405 -Netdata data collection plugins can be developed in any language. Most of our application collectors though are developed in [Go](https://github.com/netdata/go.d.plugin).

406 -

407 -</details>

262 +---

263

264 ## FAQ

265

411 -### :shield: Is Netdata secure?

412 -

413 -Of course, it is! We do our best to ensure it is!

414 -

415 -<details><summary>Click to see detailed answer ...</summary>

416 -

266 +<details>

267 +<summary>Is Netdata secure?</summary>

268

418 -We understand that Netdata is a software piece installed on millions of production systems across the world. So, it is important for us, Netdata to be as secure as possible:

269 +Yes. Netdata follows [OpenSSF best practices](https://bestpractices.coreinfrastructure.org/en/projects/2231), has a security-first design, and is regularly audited by the community.

270

420 -- We follow the [Open Source Security Foundation](https://bestpractices.coreinfrastructure.org/en/projects/2231) best practices.

421 -- We have given great attention to detail when it comes to security design. Check out our [security design](/docs/security-and-privacy-design/README.md).

422 -- Netdata is a popular open-source project and is frequently tested by many security analysts.

423 -- Check also our [security policies and advisories published so far](https://github.com/netdata/netdata/security).

271 +* [Security design](https://learn.netdata.cloud/docs/security-and-privacy-design)

272 +* [Security policies and advisories](https://github.com/netdata/netdata/security)

273

425 -

274 </details>

275

428 -### :cyclone: Will Netdata consume significant resources on my servers?

276 +<details>

277 +<summary>Does Netdata use a lot of resources?</summary>

278

430 -No, it will not! We promise this will be fast!

279 +No. Even with ML and per-second metrics, Netdata uses minimal resources.

280

432 -<details><summary>Click to see detailed answer ...</summary>

433 -

281 +* \~5% CPU and 150MiB RAM by default on production systems

282 +* <1% CPU and \~100MiB RAM when ML and alerts are disabled and using ephemeral storage

283 +* Parents scale to millions of metrics per second with appropriate hardware

284

435 -Although each Netdata Agent is a complete monitoring solution packed into a single application, and despite the fact that Netdata collects **every metric every single second** and trains **multiple ML models** per metric, you will find that Netdata has amazing performance! In many cases, it outperforms other monitoring solutions that have significantly fewer features or far smaller data collection rates.

285 +> [!NOTE]

286 +> You can use the **Netdata Monitoring** section in the dashboard to inspect its resource usage.

287

437 -This is what you should expect:

438 -

439 -- For production systems, each Netdata Agent with default settings (everything enabled, ML, Health, DB) should consume about 5% CPU utilization of one core and about 150 MiB or RAM.

440 -

441 - By using a Netdata parent and streaming all metrics to that parent, you can disable ML & health and use an ephemeral DB (like `alloc`) on the children, leading to utilization of about 1% CPU of a single core and 100 MiB of RAM. Of course, these depend on how many metrics are collected.

442 -

443 -- For Netdata Parents, for about 1 to 2 million metrics, all collected every second, we suggest a server with 16 cores and 32GB RAM. Less than half of it will be used for data collection and ML. The rest will be available for queries.

444 -

445 -Netdata has extensive internal instrumentation to help us reveal how the resources consumed are used. All these are available in the "Netdata Monitoring" section of the dashboard. Depending on your use case, there are many options to optimize resource consumption.

446 -

447 -Even if you need to run Netdata on extremely weak embedded or IoT systems, you will find that Netdata can be tuned to be very performant.

448 -

449 -

288 </details>

289

452 -### :scroll: How much retention can I have?

453 -

454 -As much as you need!

290 +<details>

291 +<summary>How much data retention is possible?</summary>

292

456 -<details><summary>Click to see detailed answer ...</summary>

457 -

293 +As much as your disk allows.

294

459 -Netdata supports **tiering**, to downsample past data and save disk space. With default settings, it has three tiers:

295 +With Netdata you can use tiered retention:

296

461 -1. `tier 0`, with high resolution, per-second, data.

462 -2. `tier 1`, mid-resolution, per minute, data.

463 -3. `tier 2`, low-resolution, per hour, data.

297 +* Tier 0: per-second resolution

298 +* Tier 1: per-minute resolution

299 +* Tier 2: per-hour resolution

300

465 -All tiers are updated in parallel during data collection. Increase the disk space you give to Netdata to get a longer history for your metrics. Tiers are automatically chosen at query time depending on the time frame and the resolution requested.

466 -

467 -

468 -</details>

469 -

470 -### :rocket: Does it scale? I really have a lot of servers!

471 -

472 -Netdata is designed to scale and can handle large volumes of data.

473 -

474 -<details><summary>Click to see detailed answer ...</summary>

475 -

476 -Netdata is a distributed monitoring solution. You can scale it to infinity by spreading Netdata Agents across your infrastructure.

477 -

478 -With the streaming feature of the Agent, we can support monitoring ephemeral servers but also allow the creation of "monitoring islands" where metrics are aggregated to a few servers (Netdata Parents) for increased retention, or for offloading production systems.

479 -

480 -- :airplane: Netdata Parents provide great vertical scalability, so you can have as big parents as the CPU, RAM and Disk resources you can dedicate to them. In our lab, we constantly stress test Netdata Parents with several million metrics collected per second, to ensure it is reliable, stable, and robust at scale.

481 -

482 -- :rocket: In addition, Netdata Cloud provides virtually unlimited horizontal scalability. It "merges" all the Netdata parents you have into one unified infrastructure at query time. Netdata Cloud itself is probably the biggest single installation monitoring platform ever created, currently monitoring about 100k online servers with about 10k servers changing state (added/removed) per day!

483 -

484 -Example: the following chart comes from a single Netdata Parent. As you can see on it, 244 nodes stream to it metrics of about 20k running containers. On this specific chart, there are three dimensions per container, so a total of about 60k time-series queries are executed to present it.

485 -

486 -![image](https://github.com/netdata/netdata/assets/2662304/33db4aed-86af-4018-a547-e70643308f25)

487 -

488 -

489 -</details>

490 -

491 -### :floppy_disk: My production servers are very sensitive in disk I/O. Can I use Netdata?

492 -

493 -Yes, you can!

494 -

495 -<details><summary>Click to see detailed answer ...</summary>

496 -

497 -

498 -The Netdata Agent has been designed to spread disk writes across time. Each metric is flushed to disk every 17 minutes (1000 seconds), but metrics are flushed evenly across time, at an almost constant rate. Also, metrics are packed into bigger blocks we call `extents` and are compressed with ZSTD before saving them, to minimize the number of I/O operations made.

499 -

500 -The Netdata Agent also employs direct I/O for all its database operations. By managing its own caches, Netdata avoids overburdening system caches, facilitating a harmonious coexistence with other applications.

501 -

502 -Single node Agents (not Parents), should have a constant write rate of about 50 KiB/s or less, with some spikes above that every minute (flushing of tier 1) and higher spikes every hour (flushing of tier 2).

503 -

504 -Health Alerts and Machine-Learning run queries to evaluate their expressions and learn from the metrics' patterns. These are also spread over time, so there should be an almost constant read rate too.

505 -

506 -To make Netdata not use the disks at all, we suggest the following:

507 -

508 -1. Use database mode `alloc` or `ram` to disable writing metric data to disk.

509 -2. Configure streaming to push in real-time all metrics to a Netdata Parent. The Netdata Parent will maintain metrics on disk for this node.

510 -3. Disable ML and health on this node. The Netdata Parent will do them for this node.

511 -4. Use the Netdata Parent to access the dashboard.

512 -

513 -Using the above, the Netdata Agent on your production system will not use a disk.

514 -

515 -

301 +These are queried automatically based on the zoom level.

302 </details>

303

518 -### :raised_eyebrow: How is Netdata different from a Prometheus and Grafana setup?

519 -

520 -Netdata is a "ready to use" monitoring solution. Prometheus and Grafana are tools to build your own monitoring solution.

521 -

522 -Netdata is also a lot faster, requires significantly fewer resources and puts almost no stress on the server it runs. For a performance comparison check [this blog](https://blog.netdata.cloud/netdata-vs-prometheus-performance-analysis/).

523 -

524 -<details><summary>Click to see detailed answer ...</summary>

525 -

526 -

527 -First, we have to say that Prometheus as a time-series database and Grafana as a visualizer are excellent tools for what they do.

528 -

529 -However, we believe that such a setup is missing a key element: A Prometheus and Grafana setup assumes that you know everything about the metrics you collect, and you understand deeply how they’re structured, they should be queried and visualized.

304 +<details>

305 +<summary>Can Netdata scale to many servers?</summary>

306

531 -In reality, this setup has a lot of problems. The vast number of technologies, operating systems, and applications we use in our modern stacks makes it impossible for any single person to know and understand everything about anything. We get testimonials regularly from Netdata users across the biggest enterprises, that Netdata manages to reveal issues, anomalies and problems they weren’t aware of, and they didn't even have the means to find or troubleshoot.

307 +Yes. With Netdata you can:

308

533 -So, the biggest difference of Netdata to Prometheus, and Grafana, is that we decided that the tool needs to have a much better understanding of the components, the applications, and the metrics it monitors.

309 +* Scale horizontally with many Agents

310 +* Scale vertically with powerful Parents

311 +* Scale infinitely via Netdata Cloud

312

535 -- When compared to Prometheus, Netdata needs for each metric much more than just a name, some labels, and a value over time. A metric in Netdata is a structured entity that correlates with other metrics in a certain way and has specific attributes that depict how it should be organized, treated, queried, and visualized. We call this the NIDL (Nodes, Instances, Dimensions, Labels) framework.

313 +> [!NOTE]

314 +> You can use Netdata Cloud to merge many independent infrastructures into one logical view.

315

537 - Maintaining such an index is a challenge: first, because the raw metrics collected do not provide this information, so we have to add it, and second because we need to maintain this index for the lifetime of each metric, which with our current database retention, it is usually more than a year.

538 -

539 - At the same time, Netdata provides better retention than Prometheus due to database tiering, scales easier than Prometheus due to streaming, supports anomaly detection, and it has a metrics scoring engine to find the needle in the haystack when needed.

540 -

541 -- When compared to Grafana, Netdata is fully automated. Grafana has more customization capabilities than Netdata, but Netdata presents fully functional dashboards by itself, and most importantly, it gives you the means to understand, analyze, filter, slice and dice the data without the need for you to edit queries or be aware of any peculiarities the underlying metrics may have.

542 -

543 - Furthermore, to help you when you need to find the needle in the haystack, Netdata has advanced troubleshooting tools provided by the Netdata metrics scoring engine, that allows it to score metrics based on their anomaly rate, their differences or similarities for any given time frame.

544 -

545 -Still, if you’re already familiar with Prometheus and Grafana, Netdata integrates nicely with them, and we have reports from users who use Netdata with Prometheus and Grafana in production.

546 -

547 -

316 </details>

317

550 -### :raised_eyebrow: How is Netdata different from DataDog, New Relic, Dynatrace, X SaaS Provider?

551 -

552 -With Netdata your data are always on-prem and your metrics are always high-resolution.

553 -

554 -<details><summary>Click to see detailed answer ...</summary>

555 -

318 +<details>

319 +<summary>Is disk I/O a concern?</summary>

320

557 -Most commercial monitoring providers face a significant challenge: they centralize all metrics to their infrastructure, and this is, inevitably, expensive. It leads them to one or more of the following:

321 +No. Netdata minimizes disk usage:

322

559 -1. be unrealistically expensive

560 -2. limit the number of metrics they collect

561 -3. limit the resolution of the metrics they collect

323 +* Metrics are flushed to disk every 17 minutes, spread out evenly

324 +* Uses direct I/O and compression (ZSTD)

325 +* Can run entirely in RAM or stream to a Parent

326

563 -As a result, they try to find a balance: collect the least possible data, but collect enough to have something useful out of it.

327 +> [!NOTE]

328 +> You can use `alloc` or `ram` mode for no disk writes.

329

565 -We, at Netdata, see monitoring in a completely different way: **monitoring systems should be built bottom-up and be rich in insights**, so we focus on each component individually to collect, store, check and visualize everything related to each of them, and we make sure that all components are monitored. Each metric is important.

566 -

567 -This is why Netdata trains multiple machine-learning models per metric, based exclusively on their own past (no sampling of data, no sharing of trained models) to detect anomalies based on the specific use case and workload each component is used.

568 -

569 -This is also why Netdata alerts are attached to components (instances) and are configured with dynamic thresholds and rolling windows, instead of static values.

570 -

571 -The distributed nature of Netdata helps scale this approach: your data is spread inside your infrastructure, as close to the edge as possible. Netdata is not one data lane. Each Netdata Agent is a data lane, and all of them together build a massive distributed metrics processing pipeline that ensures all your infrastructure components and applications are monitored and operating as they should.

572 -

573 -

330 </details>

331

576 -### :raised_eyebrow: How is Netdata different from Nagios, Icinga, Zabbix, etc.?

577 -

578 -Netdata offers real-time, comprehensive monitoring and the ability to monitor everything without any custom configuration required.

579 -

580 -<details><summary>Click to see detailed answer ...</summary>

581 -

582 -

583 -While Nagios, Icinga, Zabbix, and other similar tools are powerful and highly customizable, they can be complex to set up and manage. Their flexibility often comes at the cost of ease-of-use, especially for users who aren’t systems administrators or don’t have extensive experience with these tools. Additionally, these tools generally require you to know what you want to monitor in advance and configure it explicitly.

332 +<details>

333 +<summary>How is Netdata different from Prometheus + Grafana?</summary>

334

585 -Netdata, on the other hand, takes a different approach. It provides a "ready to use" monitoring solution with a focus on simplicity and comprehensiveness. It automatically detects and starts monitoring many different system metrics and applications out-of-the-box, without any need for custom configuration.

335 +With Netdata you get a complete monitoring solution—not just tools.

336

587 -In comparison to these traditional monitoring tools, Netdata:

337 +* No manual setup or dashboards needed

338 +* Built-in ML, alerts, dashboards, and correlations

339 +* More efficient and easier to deploy

340

589 -- Provides real-time, high-resolution metrics, as opposed to the often minute-level granularity that tools like Nagios, Icinga, and Zabbix provide.

341 +> [!NOTE]

342 +> [Performance comparison](https://blog.netdata.cloud/netdata-vs-prometheus-performance-analysis/)

343

591 -- Automatically generates meaningful, organized, and interactive visualizations of the collected data. Unlike other tools, where you have to manually create and organize graphs and dashboards, Netdata takes care of this for you.

592 -

593 -- Applies machine learning to each individual metric to detect anomalies, providing more insightful and relevant alerts than static thresholds.

594 -

595 -- Designed to be distributed, so your data is spread inside your infrastructure, as close to the edge as possible. This approach is more scalable and avoids the potential bottleneck of a single centralized server.

596 -

597 -- Has a more modern and user-friendly interface, allowing anyone, not just experienced administrators, to easily assess the health and performance of their systems.

598 -

599 -Even if you're already using Nagios, Icinga, Zabbix, or similar tools, you can use Netdata alongside them to augment your existing monitoring capabilities with real-time insights and user-friendly dashboards.

600 -

601 -

344 </details>

345

604 -### :flushed: I feel overwhelmed by the amount of information in Netdata. What should I do?

605 -

606 -Netdata is designed to provide comprehensive insights, but we understand that the richness of information might sometimes feel overwhelming. Here are some tips on how to navigate and use Netdata effectively...

607 -

608 -<details><summary>Click to see detailed answer ...</summary>

609 -

346 +<details>

347 +<summary>How is Netdata different from commercial SaaS tools?</summary>

348

611 -Netdata is indeed a very comprehensive monitoring tool. It's designed to provide you with as much information as possible about your system and applications, so that you can understand and address any issues that arise. However, we understand that the sheer amount of data can sometimes be overwhelming.

349 +With Netdata you can store all metrics on your infrastructure—no sampling, no aggregation, no loss.

350

613 -Here are some suggestions on how to manage and navigate this wealth of information:

351 +* High-resolution metrics by default

352 +* ML per metric, not shared models

353 +* Unlimited scalability without skyrocketing cost

354

615 -1. **Start with the Metrics Dashboard**

616 - Netdata's Metrics Dashboard provides a high-level summary of your system's status. We have added summary tiles on almost every section, you reveal the information that is more important. This is a great place to start, as it can help you identify any major issues or trends at a glance.

617 -

618 -2. **Use the Search Feature**

619 - If you're looking for specific information, you can use the search feature to find the relevant metrics or charts. This can help you avoid scrolling through all the data.

620 -

621 -3. **Customize your Dashboards**

622 - Netdata allows you to create custom dashboards, which can help you focus on the metrics that are most important to you. Sign-in to Netdata and there you can have your custom dashboards. (coming soon to the Agent dashboard too)

623 -

624 -4. **Leverage Netdata's Anomaly Detection**

625 - Netdata uses machine learning to detect anomalies in your metrics. This can help you identify potential issues before they become major problems. We have added an `AR` button above the dashboard table of contents to reveal the anomaly rate per section so that you can spot what could need your attention.

626 -

627 -5. **Take Advantage of Netdata's Documentation and Blogs**

628 - Netdata has extensive documentation that can help you understand the different metrics and how to interpret them. You can also find tutorials, guides, and best practices there.

629 -

630 -Remember, it's not necessary to understand every single metric or chart right away. Netdata is a powerful tool, and it can take some time to fully explore and understand all of its features. Start with the basics and gradually delve into more complex metrics as you become more comfortable with the tool.

631 -

632 -

355 </details>

356

635 -### :cloud: Do I have to subscribe to Netdata Cloud?

636 -

637 -Netdata Cloud delivers the full suite of features and functionality that Netdata offers, including a free community tier.

357 +<details>

358 +<summary>Can Netdata run alongside Nagios, Zabbix, etc.?</summary>

359

639 -While our default onboarding process encourages users to take advantage of Netdata Cloud, including a complimentary one-month trial of our full business product, it is not mandatory. Users can bypass this process entirely and still use the Netdata Agents along with the Netdata UI, without the need to sign up for Netdata Cloud.

360 +Yes. You can use Netdata together with traditional tools.

361

641 -<details><summary>Click to see detailed answer ...</summary>

642 -

362 +With Netdata you get:

363

644 -The Netdata Agent dashboard and the Netdata Cloud dashboard are the same. Still, Netdata Cloud provides additional features that the Netdata Agent is not capable of. These include:

364 +* Real-time, high-resolution monitoring

365 +* Zero configuration and auto-generated dashboards

366 +* Anomaly detection and advanced visualization

367

646 -1. Access your infrastructure from anywhere.

647 -2. Have SSO to protect sensitive features.

648 -3. Customizable (custom dashboards and other settings are persisted when you’re signed in to Netdata Cloud)

649 -4. Configuration of Alerts and Data Collection from the UI

650 -5. Security (Role-Based Access Control).

651 -6. Horizontal Scalability ("blend" multiple independent parents in one uniform infrastructure)

652 -7. Central Dispatch of Alert Notifications (even when multiple independent parents are involved)

653 -8. Mobile App for Alert Notifications

654 -

655 -We encourage you to support Netdata by buying a Netdata Cloud subscription. A successful Netdata is a Netdata that evolves and gets improved to provide simpler, faster and easier monitoring for all of us.

656 -

657 -For organizations that need a fully on-prem solution, we provide Netdata Cloud for on-prem installation. [Contact us for more information](mailto:info@netdata.cloud).

658 -

659 -

368 </details>

369

662 -### :mag_right: What does the anonymous telemetry collected by Netdata entail?

663 -

664 -Your privacy is our utmost priority. As part of our commitment to improving Netdata, we rely on anonymous telemetry data from our users who choose to leave it enabled. This data greatly informs our decision-making processes and contributes to the future evolution of Netdata.

665 -

666 -Should you wish to disable telemetry, instructions for doing so are provided in our installation guides.

667 -

668 -<details><summary>Click to see detailed answer ...</summary>

669 -

670 -

671 -Netdata is in a constant state of growth and evolution. The decisions that guide this development are ideally rooted in data. By analyzing anonymous telemetry data, we can answer questions such as "What features are being used frequently?", "How do we prioritize between potential new features?" and "What elements of Netdata are most important to our users?"

370 +<details>

371 +<summary>What if I feel overwhelmed?</summary>

372

673 -By leaving anonymous telemetry enabled, users indirectly contribute to shaping Netdata's roadmap, providing invaluable information that helps us prioritize our efforts for the project and the community.

373 +You can start small:

374

675 -We are aware that for privacy or regulatory reasons, not all environments can allow telemetry. To cater to this, we’ve simplified the process of disabling telemetry:

375 +* Use the dashboard's table of contents and search

376 +* Explore anomaly scoring ("AR" toggle)

377 +* Create custom dashboards in Netdata Cloud

378

677 -- During installation, you can append `--disable-telemetry` to our `kickstart.sh` script, or

678 -- Create the file `/etc/netdata/.opt-out-from-anonymous-statistics` and then restart Netdata.

379 +> [!NOTE]

380 +> [Docs and guides](https://learn.netdata.cloud/guides)

381

680 -These steps will disable the anonymous telemetry for your Netdata installation.

681 -

682 -Please note, even with telemetry disabled, Netdata still requires a [Netdata Registry](https://learn.netdata.cloud/docs/configuring/securing-netdata-agents/registry) for alert notifications' Call To Action (CTA) functionality. When you click an alert notification, it redirects you to the Netdata Registry, which then directs your web browser to the specific Netdata Agent that issued the alert for further troubleshooting. The Netdata Registry learns the URLs of your Agents when you visit their dashboards.

683 -

684 -Any Netdata Agent can act as a Netdata Registry. Designate one Netdata Agent as your Registry, read more [here](https://learn.netdata.cloud/docs/netdata-agent/configuration/registry).

685 -

686 -

382 </details>

383

689 -### :smirk: Who uses Netdata?

690 -

691 -Netdata is a widely adopted project...

692 -

693 -<details><summary>Click to see detailed answer ...</summary>

694 -

695 -

696 -Browse the [Netdata stargazers on GitHub](https://github.com/netdata/netdata/stargazers) to discover users from renowned companies and enterprises, such as ABN AMRO Bank, AMD, Amazon, Baidu, Booking.com, Cisco, Delta, Facebook, Google, IBM, Intel, Logitech, Netflix, Nokia, Qualcomm, Realtek Semiconductor Corp, Redhat, Riot Games, SAP, Samsung, Unity, Valve, and many others.

697 -

698 -Netdata also enjoys significant usage in academia, with notable institutions including New York University, Columbia University, New Jersey University, Seoul National University, University College London, among several others.

384 +<details>

385 +<summary>Do I have to use Netdata Cloud?</summary>

386

700 -And, Netdata is also used by many governmental organizations worldwide.

387 +No. Netdata Cloud is optional.

388

702 -In a nutshell, Netdata proves invaluable for:

389 +Netdata works without it, but with Cloud you can:

390

704 -- **Infrastructure intensive organizations**

705 - Such as hosting/cloud providers and companies with hundreds or thousands of nodes, who require a high-resolution, real-time monitoring solution for a comprehensive view of all their components and applications.

391 +* Access remotely with SSO

392 +* Save dashboard customizations

393 +* Configure alerts centrally

394 +* Collaborate with role-based access

395

707 -- **Technology operators**

708 - Those in need of a standardized, comprehensive solution for round-the-clock operations. Netdata not only facilitates operational automation and provides controlled access for their operations engineers, but also enhances skill development over time.

709 -

710 -- **Technology startups**

711 - Who seek a feature-rich monitoring solution from the get-go.

712 -

713 -- **Freelancers**

714 - Who seek a simple, efficient and straightforward solution without sacrificing performance and outcomes.

715 -

716 -- **Professional SysAdmins and DevOps**

717 - Who appreciate the fine details and understand the value of holistic monitoring from the ground up.

718 -

719 -- **Everyone else**

720 - All of us, who are tired of the inefficiency in the monitoring industry and would love a refreshing change and a breath of fresh air. :slightly_smiling_face:

721 -

722 -

396 </details>

397

725 -### :globe_with_meridians: Is Netdata open-source?

726 -

727 -The **Netdata Agent** is open-source, but the **overall Netdata ecosystem** is a hybrid solution, combining open-source and closed-source components.

728 -

729 -<details><summary>Click to see detailed answer ...</summary>

730 -

731 -

732 -Open-source is about sharing intellectual property with the world, and at Netdata, we embrace this philosophy wholeheartedly.

733 -

734 -The **Netdata Agent**, the core of our ecosystem and the engine behind all our observability features, is fully open-source. Licensed under GPLv3+, the Netdata Agent represents our commitment to open-sourcing innovation in a wide array of observability technologies, including data collection, database design, query engines, observability data modeling, machine learning and unsupervised anomaly detection, high-performance edge computing, real-time monitoring, and more.

735 -

736 -**The Netdata Agent is our gift to the world**, ensuring that the cutting-edge advancements we've developed are freely accessible to everyone.

737 -

738 -However, as a privately funded company, we also need to monetize our open-source software to demonstrate product-market fit and sustain our growth.

739 -

740 -Traditionally, open-source projects have often used the open-core model, where a basic version of the software is open-source, and additional features are reserved for a commercial, closed-source version. This approach can limit access to advanced innovations, as most of these remain closed-source.

741 -

742 -At Netdata, we take a slightly different path. We don't create a separate enterprise version of our product. Instead, all users - both commercial and non-commercial - use the same Netdata Agent, ensuring that all of our observability innovations are always open source.

743 -

744 -To experience the full capabilities of the Netdata ecosystem, users need to combine the open-source components with our closed-source offerings. The complete product still remains free to use.

398 +<details>

399 +<summary>What telemetry does Netdata collect?</summary>

400

746 -The closed-source components include:

401 +Anonymous telemetry helps improve the product. You can disable it:

402

748 -- **Netdata UI**: This is closed-source but free to use with the Netdata Agents and Netdata Cloud. It’s also publicly available via a CDN.

749 -- **Netdata Cloud**: A commercial product available both as an on-premises installation and as a SaaS solution, with a free community tier.

403 +* Add `--disable-telemetry` to the installer, or

404 +* Create `/etc/netdata/.opt-out-from-anonymous-statistics` and restart Netdata

405

751 -By balancing open-source and closed-source components, we ensure that all users have access to our innovations while sustaining our ability to grow and innovate as a company.

406 +> [!NOTE]

407 +> Telemetry helps us understand usage, not track users. No private data is collected.

408

753 -

409 </details>

410

756 -### :moneybag: What is your monetization strategy?

411 +<details>

412 +<summary>Who uses Netdata?</summary>

413

758 -Netdata generates revenue through subscriptions to advanced features of Netdata Cloud and sales of on-premise and private versions of Netdata Cloud.

414 +You'll join users including:

415

760 -<details><summary>Click to see detailed answer ...</summary>

761 -

416 +* Major companies (Amazon, ABN AMRO Bank, Facebook, Google, IBM, Intel, Netflix, Samsung)

417 +* Universities (NYU, Columbia, Seoul National, UCL)

418 +* Government organizations worldwide

419 +* Infrastructure-intensive organizations

420 +* Technology operators

421 +* Startups and freelancers

422 +* SysAdmins and DevOps professionals

423

763 -Netdata generates revenue from these activities:

764 -

765 -1. **Netdata Cloud Subscriptions**

766 - Direct funding for our project's vision comes from users subscribing to Netdata Cloud's advanced features.

767 -

768 -2. **Netdata Cloud On-Prem or Private**

769 - Purchasing the on-premises or private versions of Netdata Cloud supports our financial growth.

770 -

771 -Our Open-Source Community and the free access to Netdata Cloud, contribute to Netdata in the following ways:

772 -

773 -- **Netdata Cloud Community Use**

774 - The free usage of Netdata Cloud demonstrates its market relevance. While this doesn't generate revenue, it reinforces trust among new users and aids in securing appropriate project funding.

775 -

776 -- **User Feedback**

777 - Feedback, especially issues and bug reports, is invaluable. It steers us towards a more resilient and efficient product. This, too, isn't a revenue source but is pivotal for our project's evolution.

778 -

779 -- **Anonymous Telemetry Insights**

780 - Users who keep anonymous telemetry enabled, help us make data informed decisions on refining and enhancing Netdata. This isn't a revenue stream, but knowing which features are used and how, contributes in building a better product for everyone.

781 -

782 -We don't monetize, directly or indirectly, users' or "device heuristics" data. Any data collected from community members is exclusively used for the purposes stated above.

783 -

784 -Netdata grows financially when technology intensive organizations and operators need - due to regulatory or business requirements - the entire Netdata suite on-prem or private, bundled with top-tier support. It is a win-win case for all parties involved: these companies get a battle tested, robust and reliable solution, while the broader community that helps us build this product enjoys it at no cost.

785 -

786 -

424 </details>

425

789 -## :book: Documentation

426 +---

427

791 -Netdata's documentation is available at [**Netdata Learn**](https://learn.netdata.cloud).

428 +## \:book: Documentation

429

793 -This site also hosts a number of [guides](https://learn.netdata.cloud/guides) to help newer users better understand how

794 -to collect metrics, troubleshoot via charts, export to external databases, and more.

430 +Visit [Netdata Learn](https://learn.netdata.cloud) for full documentation and guides.

431

796 -## :tada: Community

432 +> [!NOTE]

433 +> Includes deployment, configuration, alerting, exporting, troubleshooting, and more.

434

798 -

799 - <a href="https://discord.com/invite/2mEmfW735j"><img alt="Discord" src="https://img.shields.io/discord/847502280503590932?logo=discord&logoColor=white&label=chat%20on%20discord"></a>

800 - <a href="https://community.netdata.cloud"><img alt="Discourse topics" src="https://img.shields.io/discourse/topics?server=https%3A%2F%2Fcommunity.netdata.cloud%2F&logo=discourse&label=discourse%20forum"></a>

801 - <a href="https://github.com/netdata/netdata/discussions"><img alt="GitHub Discussions" src="https://img.shields.io/github/discussions/netdata/netdata?logo=github&label=github%20discussions"></a>

802 -

435 +---

436

804 -Netdata is an inclusive open-source project and community. Please read our [Code of Conduct](https://github.com/netdata/.github/blob/main/CODE_OF_CONDUCT.md).

437 +## \:tada: Community

438

439 Join the Netdata community:

440

808 -- Chat with us and other community members on [Discord](https://discord.com/invite/2mEmfW735j).

809 -- Start a discussion on [GitHub discussions](https://github.com/netdata/netdata/discussions).

810 -- Open a topic to our [community forums](https://community.netdata.cloud).

811 -

812 -> **Meet Up** :people_holding_hands::people_holding_hands::people_holding_hands:

813 -> The Netdata team and community members have regular online meetups.

814 -> **You are welcome to join us!**

815 -> [Click here for the schedule](https://www.meetup.com/netdata/events/).

816 -

817 -You can also find Netdata on:

818 -[Twitter](https://twitter.com/netdatahq) | [YouTube](https://www.youtube.com/c/Netdata) | [Reddit](https://www.reddit.com/r/netdata/) | [LinkedIn](https://www.linkedin.com/company/netdata-cloud/) | [StackShare](https://stackshare.io/netdata) | [Product Hunt](https://www.producthunt.com/posts/netdata-monitoring-agent/) | [Repology](https://repology.org/metapackage/netdata/versions) | [Facebook](https://www.facebook.com/linuxnetdata/)

819 -

820 -## :pray: Contribute

821 -

822 -

823 - <a href="https://github.com/netdata/netdata/graphs/contributors"><img alt="Open Source Contributors" src="https://img.shields.io/github/contributors/netdata/netdata?label=open-source%20contributors"></a>

824 -

825 -

826 -Contributions are essential to the success of open-source projects. In other words, we need your help to keep Netdata great!

827 -

828 -What is a contribution? All the following are highly valuable to Netdata:

829 -

830 -1. **Let us know of the best practices you believe should be standardized**

831 - Netdata should out-of-the-box detect as many infrastructure issues as possible. By sharing your knowledge and experiences, you help us build a monitoring solution that has baked into it all the best-practices about infrastructure monitoring.

832 -

833 -2. **Let us know if Netdata is not perfect for your use case**

834 - We aim to support as many use cases as possible and your feedback can be invaluable. Open a GitHub issue, or start a GitHub discussion about it, to discuss how you want to use Netdata and what you need.

441 +* [Discord](https://discord.com/invite/2mEmfW735j)

442 +* [Forum](https://community.netdata.cloud)

443 +* [GitHub Discussions](https://github.com/netdata/netdata/discussions)

444

836 - Although we can't implement everything imaginable, we try to prioritize development on use-cases that are common to our community, are in the same direction we want Netdata to evolve and are aligned with our roadmap.

445 +> [!NOTE]

446 +> [Code of Conduct](https://github.com/netdata/.github/blob/main/CODE_OF_CONDUCT.md)

447

838 -3. **Support other community members**

839 - Join our community on GitHub, Discord, and Reddit. Generally, Netdata is relatively easy to set up and configure, but still people may need a little push in the right direction to use it effectively. Supporting other members is a great contribution by itself!

448 +Follow us on:

449 +[Twitter](https://twitter.com/netdatahq) | [Reddit](https://www.reddit.com/r/netdata/) | [YouTube](https://www.youtube.com/c/Netdata) | [LinkedIn](https://www.linkedin.com/company/netdata-cloud/)

450

841 -4. **Add or improve integrations you need**

842 - Integrations tend to be easier and simpler to develop. If you would like to contribute your code to Netdata, we suggest that you start with the integrations you need, which Netdata doesn’t currently support.

843 -

844 -General information about contributions:

451 +---

452

846 -- Check our [Security Policy](https://github.com/netdata/netdata/security/policy).

847 -- Found a bug? Open a [GitHub issue](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml&title=%5BBug%5D%3A+).

848 -- Read our [Contributing Guide](https://github.com/netdata/.github/blob/main/CONTRIBUTING.md), which contains all the information you need to contribute to Netdata, such as improving our documentation, engaging in the community, and developing new features. We've made it as frictionless as possible, but if you need help, just ping us on our community forums!

453 +## \:pray: Contribute

454

850 -Package maintainers should read the guide on [building Netdata from source](/packaging/installer/methods/source.md) for

851 -instructions on building each Netdata component from the source and preparing a package.

455 +We welcome your contributions.

456

853 -## License

457 +Ways you help us stay sharp:

458

855 -The Netdata ecosystem consists of three key parts:

459 +* Share best practices and monitoring insights

460 +* Report issues or missing features

461 +* Improve documentation

462 +* Develop new integrations or collectors

463 +* Help users in forums and chats

464

857 -- **Netdata Agent**: The heart of the Netdata ecosystem, the Netdata Agent is an open-source tool that must be installed on all systems monitored by Netdata. It offers a wide range of essential features, including data collection via various plugins, an embedded high-performance time-series database (dbengine), unsupervised anomaly detection powered by edge-trained machine learning, alerting and notifications, as well as query and scoring engines with associated APIs. Additionally, it supports exporting data to third-party monitoring systems, among other capabilities.

465 +> [!NOTE]

466 +> [Contribution guide](https://github.com/netdata/.github/blob/main/CONTRIBUTING.md)

467

859 - The Netdata Agent is released under the [GPLv3+ license](https://github.com/netdata/netdata/blob/master/LICENSE) and redistributes several other open-source tools and libraries, which are listed in the [Netdata Agent third-party licenses](https://github.com/netdata/netdata/blob/master/REDISTRIBUTED.md).

468 +---

469

861 -- **Netdata Cloud**: A commercial, closed-source component, Netdata Cloud enhances the capabilities of the open-source Netdata Agent by providing horizontal scalability, centralized alert notification dispatch (including a mobile app), user management, role-based access control, and other enterprise-grade features. It is available both as a SaaS solution and for on-premises deployment, with a free-to-use community tier also offered.

470 +## \:scroll: License

471

863 -- **Netdata UI**: The Netdata UI is closed-source, and handles all visualization and dashboard functionalities related to metrics, logs and other collected data, as well as the central configuration and management of the Netdata ecosystem. It serves both the Netdata Agent and Netdata Cloud. The Netdata UI is distributed in binary form with the Netdata Agent and is publicly accessible via a CDN, licensed under the [Netdata Cloud UI License 1 (NCUL1)](https://app.netdata.cloud/LICENSE.txt). It integrates third-party open-source components, detailed in the [Netdata UI third-party licenses](https://app.netdata.cloud/3D_PARTY_LICENSES.txt).

472 +The Netdata ecosystem includes:

473

865 -The binary installation packages provided by Netdata include the Netdata Agent and the Netdata UI. Since the Netdata Agent is open-source, it is frequently packaged by third parties (e.g., Linux Distributions) excluding the closed-source components (Netdata UI is not included). While their packages can still be useful in providing the necessary back-ends and the APIs of a fully functional monitoring solution, we recommend using the installation packages we provide to experience the full feature set of Netdata.

474 +* **Netdata Agent** – Open-source core (GPLv3+). **Includes** data collection, storage, ML, alerting, APIs and **redistributes** several other open-source tools and libraries.

475 + * [Netdata Agent License](https://github.com/netdata/netdata/blob/master/LICENSE)

476 + * [Netdata Agent Redistributed](https://github.com/netdata/netdata/blob/master/REDISTRIBUTED.md)

477 +* **Netdata UI** – Closed-source but free to use with Netdata Agent and Cloud. Delivered via CDN. It integrates third-party open-source components.

478 + * [Netdata Cloud UI License](https://app.netdata.cloud/LICENSE.txt)

479 + * [Netdata UI third-party licenses](https://app.netdata.cloud/3D_PARTY_LICENSES.txt)

480 +* **Netdata Cloud** – Closed-source, with free and paid tiers. Adds remote access, SSO, scalability.

Update Netdata README (#20251)