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.
Sébastien Maccagnoni aa42f9eecd
Improve installation method for Alpine (#11035)
7 hours ago
.devcontainer Support VS Code container devenv (#10723) 2 months ago
.github Limit maximum concurrent CI jobs to avoid blocking other CI. (#11057) 1 week ago
.travis Assorted fixes for Travis CI code. (#10981) 3 weeks ago
aclk ACLK new cloud architecture new TBEB (#10941) 1 week ago
backends Backend chart filtering backward compatibility fix (#11002) 2 weeks ago
build Spelling build (#10909) 3 weeks ago
build_external Spelling build (#10909) 3 weeks ago
claim Add functionality to store node_id for a host (#11059) 7 days ago
cli Docs housekeeping for SEO and syntax, part 1 (#10388) 4 months ago
collectors cgroups: fix network interfaces detection when using `virsh` (#11096) 8 hours ago
contrib Spelling build (#10428) 1 month ago
daemon Add an event when an incomplete agent shutdown is detected #11078 1 day ago
database Add functionality to store node_id for a host (#11059) 7 days ago
diagrams Docs housekeeping for SEO and syntax, part 1 (#10388) 4 months ago
docs Improve dashboard documentation (part 2) (#11065) 22 hours ago
exporting Allow the remote write configuration have multiple destinations (#11005) 2 weeks ago
health Add a module for ZFS pool state (#11071) 22 hours ago
libnetdata Ebpf directory cache (#10855) 3 days ago
mqtt_websockets@232c761830 mqtt-c coverity fixes (#10851) 1 month ago
packaging Improve installation method for Alpine (#11035) 7 hours ago
parser Spelling md (#10508) 4 months ago
registry Move global stats to a separate thread (#10991) 2 weeks ago
spawn spelling: bidirectional (#10918) 3 weeks ago
streaming Store null claim id in the database for non claimed children (#11036) 1 week ago
system Fix systemd comment syntax (#10066) 7 months ago
tests Spelling tests (#10920) 3 weeks ago
web Add a module for ZFS pool state (#11071) 22 hours ago
.clang-format Fine tune clang-format (#7271) 3 weeks ago
.codacy.yml Improving the ACLK performance - initial changes (#8399) 1 year ago
.codeclimate.yml modularized all source code (#4391) 3 years ago
.csslintrc added codeclimate coverage 4 years ago
.dockerignore Adds Docker based build system for Binary Packages, CI/CD, Smoke Testing and Development. (#7735) 1 year ago
.eslintignore added codeclimate coverage 4 years ago
.eslintrc added codeclimate coverage 4 years ago
.gitattributes Add a .gitattributes file (#6381) 2 years ago
.gitignore Move ACLK Legacy into a subfolder (#10265) 4 months ago
.gitmodules Adds ACLK-NG as fallback(#10315) 2 months ago
.lgtm.yml Split js 2 (#4581) 3 years ago
.mlc_config.json GitHub action markdown link check update (#10474) 4 months ago
.remarkignore add to .remarkignore (#6671) 2 years ago
.remarkrc.js Change lint standard for lists (#10371) 4 months ago
.squash.yml Squash integration (#5566) 2 years ago
.travis.yml Assorted fixes for Travis CI code. (#10981) 3 weeks ago
.yamllint.yml github/workflow: disable `document-start` yamllint check (#8522) 1 year ago Docs housekeeping for SEO and syntax, part 1 (#10388) 4 months ago Spelling md (#10508) 4 months ago [ci skip] create nightly packages and update changelog 14 hours ago
CMakeLists.txt Ebpf directory cache (#10855) 3 days ago
Dockerfile Remove the confusion around the multiple Dockerfile(s) we have (#8214) 1 year ago
Dockerfile.test Spelling build (#10909) 3 weeks ago Spelling md (#10508) 4 months ago
LICENSE remove license templates; add info about SPDX to main license file 3 years ago Ebpf directory cache (#10855) 3 days ago Contributing revamp, take 2 (#10956) 3 weeks ago Docs housekeeping for SEO and syntax, part 1 (#10388) 4 months ago Fix the to correctly pass REINSTALL_OPTIONS (finally) (#8808) 8 months ago
configs.signatures Drop dirty dbengine pages if disk cannot keep up (#7777) 1 year ago Add a plugin for the system clock synchronization state (#10895) 3 weeks ago Update Coverity version so that scanning works again. (#10794) 2 months ago optimized ses and added des (#4470) 3 years ago Enable IPv6 support in libwebsockets (#11079) (#11080) 1 day ago
netdata.cppcheck remove static dir config 3 years ago Spelling build (#10909) 3 weeks ago
package-lock.json fix minor vulnerability alert, updating socket-io dependency (#10557) 3 months ago
package.json fix minor vulnerability alert, updating socket-io dependency (#10557) 3 months ago


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

Latest release Build status CII Best Practices License: GPL v3+ analytics
Code Climate Codacy LGTM C LGTM PYTHON


Netdata's distributed, real-time monitoring Agent collects thousands of metrics from systems, hardware, containers, and applications with zero configuration. 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.

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

Latest release: v1.30.0, March 31, 2021

The v1.30.0 release of Netdata brings major improvements to our packaging and completely replaces Google Analytics/GTM for product telemetry. We're also releasing the first changes in an upcoming overhaul to both our dashboard UI/UX and the suite of preconfigured alarms that comes with every installation.



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.
  • 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

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.

bash <(curl -Ss

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.

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.".