Real-time performance monitoring, done right!
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
netdatabot 93a2019faa
[ci skip] Update changelog and version for nightly build: v1.37.0-199-nightly.
19 hours ago
.devcontainer Support VS Code container devenv (#10723) 2 years ago
.github Assorted infrastructure cleanup. (#14223) 3 days ago
aclk Introduce the new Structure of the documentation (#13915) 3 days ago
build allow netdata installer to install and run netdata as any user (#13780) 4 months ago
build_external remove deprecated fping.plugin in accordance with v1.37.0 deprecation notice (#14073) 2 months ago
claim Introduce the new Structure of the documentation (#13915) 3 days ago
cli Introduce the new Structure of the documentation (#13915) 3 days ago
collectors Improve ebpf exit (#14270) 1 day ago
contrib Assorted infrastructure cleanup. (#14223) 3 days ago
daemon DBENGINE v2 - improvements part 10 (#14332) 2 days ago
database DBENGINE v2 - improvements part 10 (#14332) 2 days ago
diagrams Replace individual collector images/links on infographic (#14262) 2 weeks ago
docs Introduce the new Structure of the documentation (#13915) 3 days ago
exporting Introduce the new Structure of the documentation (#13915) 3 days ago
health minor fix on notification doc (Discord) (#14339) 1 day ago
libnetdata Add Collector log (#14309) 3 days ago
ml DBENGINE v2 - improvements part 9 (#14326) 3 days ago
mqtt_websockets@684fa17afb remove mqtt-c from websockets (#14181) 5 days ago
packaging [ci skip] Update changelog and version for nightly build: v1.37.0-199-nightly. 19 hours ago
parser Introduce the new Structure of the documentation (#13915) 3 days ago
registry Introduce the new Structure of the documentation (#13915) 3 days ago
spawn Improve file descriptor closing loops (#14213) 1 week ago
streaming DBENGINE v2 - improvements part 10 (#14332) 2 days ago
system fix(pacakging): fix cpu/memory metrics when running inside LXC container as systemd service (#14255) 2 weeks ago
tests Assorted infrastructure cleanup. (#14223) 3 days ago
web DBENGINE v2 - improvements part 10 (#14332) 2 days ago
.clang-format Fine tune clang-format (#7271) 2 years ago
.codacy.yml codacy/lgtm ignore judy sources (#13411) 6 months ago
.codeclimate.yml Remove node.d.plugin and relevant files (#12769) 9 months ago
.dockerignore Restore a broken symbolic link (#12923) 9 months ago
.eslintignore Bundle the react dashboard code into the agent repo directly. (#11139) 2 years ago
.eslintrc added codeclimate coverage 6 years ago
.gitattributes Add a .gitattributes file (#6381) 4 years ago
.gitignore remove deprecated fping.plugin in accordance with v1.37.0 deprecation notice (#14073) 2 months ago
.gitmodules Remove anomaly detector (#13657) 4 months ago
.mlc_config.json GitHub action markdown link check update (#10474) 2 years ago
.yamllint.yml Clean up YAML files in the repository. (#11570) 1 year ago Docs: Removed Google Analytics tags (#12145) 12 months ago Docs: Removed Google Analytics tags (#12145) 12 months ago [ci skip] Update changelog and version for nightly build: v1.37.0-199-nightly. 19 hours ago
CMakeLists.txt remove mqtt-c from websockets (#14181) 5 days ago
Dockerfile Remove the confusion around the multiple Dockerfile(s) we have (#8214) 3 years ago
Dockerfile.test Spelling build (#10909) 2 years ago Spelling md (#10508) 2 years ago
LICENSE remove license templates; add info about SPDX to main license file 4 years ago Assorted infrastructure cleanup. (#14223) 3 days ago Assorted infrastructure cleanup. (#14223) 3 days ago Metric correlations (#12582) 9 months ago CMake - add possibility to build without ACLK (#13736) 4 months ago
configs.signatures Drop dirty dbengine pages if disk cannot keep up (#7777) 3 years ago remove mqtt-c from websockets (#14181) 5 days ago Introduce the new Structure of the documentation (#13915) 3 days ago Bump Coverity version to latest (2022.06). (#13541) 5 months ago optimized ses and added des (#4470) 4 years ago Use "getent group" instead of reading "/etc/group" to get group information (#14316) 1 day ago
netdata.cppcheck remove static dir config 4 years ago fix(packaging): add setuid for cgroup-network and ebpf.plugin in RPM (#14140) 2 months ago


Netdata is high-fidelity infrastructure monitoring and troubleshooting.
Open-source, free, preconfigured, opinionated, and always real-time.

GitHub Stars
Latest release Latest nightly build
CII Best Practices Code Climate License: GPL v3+


Netdata is a distributed, real-time, performance and health monitoring platform for systems, hardware, containers and applications, collecting thousands of useful metrics with zero configuration needed. It runs permanently on all your physical/virtual servers, containers, cloud deployments, and edge/IoT devices, and is perfectly safe to install on your systems mid-incident without any preparation.

The Netdata Agent is an enormously powerful, Open-Sourced, Single Node health monitoring and performance troubleshooting tool. It gives you the ability to automatically identify processes, collect and store metrics locally and even more - visualize all metrics without any configuration (of course you can tweak it later on if you need).

Netdata Cloud is a hosted web interface that gives you Free, real-time visibility into your Entire Infrastructure with secure access to your Netdata Agents. It provides an ability to automatically route your requests to the most relevant agents to display your metrics, based on the stored metadata (Agents topology, what metrics are collected on specific Agents as well as the retention information for each metric).

It gives you some extra features, like Metric Correlations, Anomaly Advisor, anomaly rates on every chart and much more.

Try it for yourself right now by checking out the Netdata Cloud demo space (No sign up or login needed).

Netdata's mission is to help more people troubleshoot ever more complex IT infrastructures, this is why our free community plan gives you ability to monitor unlimited number of Nodes, Containers and Metrics (custom or built-in).

Due to the distributed nature of Netdata, and to ensure high-availability of your monitoring system, please check our Data Replication recommendations to increase the data availability.

You can install Netdata on most Linux distributions (Ubuntu, Debian, CentOS, and more), container platforms (Kubernetes clusters, Docker), and many other operating systems (FreeBSD, macOS). No sudo required.

Netdata is designed by system administrators, DevOps engineers, and developers to collect everything, help you visualize metrics, troubleshoot complex performance problems, and make data interoperable with the rest of your monitoring stack.

People get addicted to Netdata. Once you use it on your systems, there's no going back! You've been warned...

Users who are addicted toNetdata



Netdata inaction

Here's what you can expect from Netdata:

  • 1s granularity: The highest possible resolution for all metrics.
  • Unlimited metrics: Netdata collects all the available metrics—the more, the better.
  • 1% CPU utilization of a single core: It's unbelievably optimized.
  • A few MB of RAM: The highly-efficient database engine stores per-second metrics in RAM and then "spills" historical metrics to disk long-term storage.
  • Minimal disk I/O: While running, Netdata only writes historical metrics and reads error and access logs.
  • Zero configuration: Netdata auto-detects everything, and can collect up to 10,000 metrics per server out of the box.
  • Zero maintenance: You just run it. Netdata does the rest.
  • Stunningly fast, interactive visualizations: The dashboard responds to queries in less than 1ms per metric to synchronize charts as you pan through time, zoom in on anomalies, and more.
  • Visual anomaly detection: Our UI/UX emphasizes the relationships between charts to help you detect the root cause of anomalies.
  • Machine learning (ML) features out of the box: Unsupervised ML-based anomaly detection, every second, every metric, zero-config! Metric correlations to help with short-term change detection. And other additional ML-based features to help make your life easier.
  • Scales to infinity: You can install it on all your servers, containers, VMs, and IoT devices. Metrics are not centralized by default, so there is no limit.
  • Several operating modes: Autonomous host monitoring (the default), headless data collector, forwarding proxy, store and forward proxy, central multi-host monitoring, in all possible configurations. Use different metrics retention policies per node and run with or without health monitoring.

Netdata works with tons of applications, notifications platforms, and other time-series databases:

  • 300+ system, container, and application endpoints: Collectors autodetect metrics from default endpoints and immediately visualize them into meaningful charts designed for troubleshooting. See everything we support.
  • 20+ notification platforms: Netdata's health watchdog sends warning and critical alarms to your favorite platform to inform you of anomalies just seconds after they affect your node.
  • 30+ external time-series databases: Export resampled metrics as they're collected to other local- and Cloud-based databases for best-in-class interoperability.

💡 Want to leverage the monitoring power of Netdata across entire infrastructure? View metrics from any number of distributed nodes in a single interface and unlock even more features with Netdata Cloud.

Get Netdata

User base Servers monitored Sessions served Docker Hub pulls
New users today New machines today Sessions today Docker Hub pulls today

Infrastructure view

Due to the distributed nature of the Netdata ecosystem, it is recommended to setup not only one Netdata Agent on your production system, but also an additional Netdata Agent acting as a Parent. A local Netdata Agent (child), without any database or alarms, collects metrics and sends them to another Netdata Agent (parent). The same parent can collect data for any number of child nodes and serves as a centralized health check engine for each child by triggering alerts on their behalf.

Netdata Cloud

Get started by signing in to and follow the setup guide.

Community version is free to use forever. No restriction on number of nodes, clusters or metrics. Unlimited alerts.

Claiming existing Agents

You can easily connect (claim) your existing Agents to the Cloud to unlock features for free and to find weaknesses before they turn into outages.

Single Node view

In case you do not need the infrastructure view of you system you can install standalone Agent and enjoy the local dashboard.

To install Netdata from source on most Linux systems (physical, virtual, container, IoT, edge), run our one-line installation script. This script downloads and builds all dependencies, including those required to connect to Netdata Cloud if you choose, and enables automatic nightly updates and anonymous statistics.

wget -O /tmp/ && sh /tmp/

To view the Netdata dashboard, navigate to http://localhost:19999, or http://NODE:19999.


You can also try out Netdata's capabilities in a Docker container:

docker run -d --name=netdata \
  -p 19999:19999 \
  -v netdataconfig:/etc/netdata \
  -v netdatalib:/var/lib/netdata \
  -v netdatacache:/var/cache/netdata \
  -v /etc/passwd:/host/etc/passwd:ro \
  -v /etc/group:/host/etc/group:ro \
  -v /proc:/host/proc:ro \
  -v /sys:/host/sys:ro \
  -v /etc/os-release:/host/etc/os-release:ro \
  --restart unless-stopped \
  --cap-add SYS_PTRACE \
  --security-opt apparmor=unconfined \

To view the Netdata dashboard, navigate to http://localhost:19999, or http://NODE:19999.

Other operating systems

See our documentation for additional operating systems, including Kubernetes, .deb/.rpm packages, and more.


When you're finished with installation, check out our single-node or infrastructure monitoring quickstart guides based on your use case.

Or, skip straight to configuring the Netdata Agent.

Read through Netdata's documentation, which is structured based on actions and solutions, to enable features like health monitoring, alarm notifications, long-term metrics storage, exporting to external databases, and more.

How it works

Netdata is a highly efficient, highly modular, metrics management engine. Its lockless design makes it ideal for concurrent operations on the metrics.

Diagram of Netdata's corefunctionality

The result is a highly efficient, low-latency system, supporting multiple readers and one writer on each metric.


This is a high-level overview of Netdata features and architecture. Click on it to view an interactive version, which has links to our documentation.

An infographic of how Netdataworks


Netdata's documentation is available at Netdata Learn.

This site also hosts a number of guides to help newer users better understand how to collect metrics, troubleshoot via charts, export to external databases, and more.


Netdata is an inclusive open-source project and community. Please read our Code of Conduct.

Find most of the Netdata team in our community forums. It's the best place to ask questions, find resources, and engage with passionate professionals. The team is also available and active in our Discord too.

You can also find Netdata on:


Contributions are the lifeblood of open-source projects. While we continue to invest in and improve Netdata, we need help to democratize monitoring!

  • Read our Contributing Guide, 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!
  • We have a whole category dedicated to contributing and extending Netdata on our community forums
  • Found a bug? Open a GitHub issue.
  • View our Security Policy.

Package maintainers should read the guide on building Netdata from source for instructions on building each Netdata component from source and preparing a package.


The Netdata Agent is GPLv3+. Netdata re-distributes other open-source tools and libraries. Please check the third party licenses.

Is it any good?


When people first hear about a new product, they frequently ask if it is any good. A Hacker News user remarked:

Note to self: Starting immediately, all raganwald projects will have a “Is it any good?” section in the readme, and the answer shall be “yes.".