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.
netdatabot d600e249a7 [Package amd64 RPM][Build latest] Package build process trigger 23 hours ago
.github Changed Docker image tagging to use semver tags for releases. (#10648) 3 days ago
.travis Fixed argument handling in `.travis/`. (#10546) 1 month ago
aclk Log ACLK cloud commands to access.log (#10697) 3 days ago
backends Spelling md (#10508) 2 months ago
build Added support for using `/etc/cron.d` for auto-updates. (#9598) 6 months ago
build_external Spelling md (#10508) 2 months ago
claim Update claiming docs for Docker containers. (#10570) 4 weeks ago
cli Docs housekeeping for SEO and syntax, part 1 (#10388) 2 months ago
collectors python.d/smartd_log: collect attribute 233 (Media Wearout Indicator (SSD)). (#10711) 3 days ago
contrib Fixed bundling of libwebsockets in binary packages. (#10460) 2 months ago
daemon Add JSON output option for buildinfo. (#10706) 3 days ago
database Add support for changing the number of pages per extent dynamically during runtime. (#10593) 6 days ago
diagrams Docs housekeeping for SEO and syntax, part 1 (#10388) 2 months ago
docs Add guide: LAMP stack monitoring (#10698) 2 days ago
exporting Don't add duplicate _total suffixes for the prometheus go.d module (#10674) 1 week ago
health Change all refs from service to systemctl (#10703) 4 days ago
libnetdata New version eBPF programs. (#10707) 4 days ago
packaging [ci skip] create nightly packages and update changelog 23 hours ago
parser Spelling md (#10508) 2 months ago
registry Add new cookie to fix 8094 (#10676) 5 days ago
spawn Make libnetdata headers compilable by C++. (#10185) 4 months ago
streaming add `_is_k8s_node` label to the host labels (#10501) 2 months ago
system Fix systemd comment syntax (#10066) 5 months ago
tests Docs housekeeping for SEO and syntax, part 1 (#10388) 2 months ago
web Log ACLK cloud commands to access.log (#10697) 3 days ago
.clang-format Add clang-format. Update Contribution guidelines. (#6677) 1 year ago
.codacy.yml Improving the ACLK performance - initial changes (#8399) 12 months ago
.codeclimate.yml modularized all source code (#4391) 2 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) 2 months ago
.lgtm.yml Split js 2 (#4581) 2 years ago
.mlc_config.json GitHub action markdown link check update (#10474) 2 months ago
.remarkignore add to .remarkignore (#6671) 2 years ago
.remarkrc.js Change lint standard for lists (#10371) 2 months ago
.squash.yml Squash integration (#5566) 1 year ago
.travis.yml Fixed handling of Docker image tags for release builds. (#10615) 4 weeks ago
.yamllint.yml github/workflow: disable `document-start` yamllint check (#8522) 10 months ago Docs housekeeping for SEO and syntax, part 1 (#10388) 2 months ago Spelling md (#10508) 2 months ago [ci skip] create nightly packages and update changelog 2 days ago
CMakeLists.txt Add Linux page cache metrics to eBPF (#10693) 4 days ago Docs housekeeping for SEO and syntax, part 1 (#10388) 2 months ago Updated contributing guidelines to suggest use of Draft PRs. (#10125) 3 months ago web/gui: Added support for per series styling for dygraphs (#8668) 2 months ago
Dockerfile Remove the confusion around the multiple Dockerfile(s) we have (#8214) 1 year ago
Dockerfile.test Remove the confusion around the multiple Dockerfile(s) we have (#8214) 1 year ago Spelling md (#10508) 2 months ago
LICENSE remove license templates; add info about SPDX to main license file 3 years ago Add Linux page cache metrics to eBPF (#10693) 4 days ago Update latest release on main README (#10590) 1 month ago Docs housekeeping for SEO and syntax, part 1 (#10388) 2 months ago Docs housekeeping for SEO and syntax, part 1 (#10388) 2 months ago Fix the to correctly pass REINSTALL_OPTIONS (finally) (#8808) 6 months ago
configs.signatures Drop dirty dbengine pages if disk cannot keep up (#7777) 1 year ago Remove unreachable #else directives in plugins. (#10523) 1 week ago Fix coverity scan (#8388) 1 year ago optimized ses and added des (#4470) 2 years ago New eBPF kernel (#10434) 2 months ago
netdata.cppcheck remove static dir config 3 years ago Fixed condition controlling use of static LWS in RPM builds. (#10661) 2 weeks ago
package-lock.json fix minor vulnerability alert, updating socket-io dependency (#10557) 1 month ago
package.json fix minor vulnerability alert, updating socket-io dependency (#10557) 1 month 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

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.29.0, February 2, 2021

The v1.29.0 release of the Netdata Agent is a maintenance release that brings incremental but necessary improvements
that make your monitoring experience more robust. We've pushed improvements and bug fixes to the installation and
update scripts, enriched our library of collectors, and focused on fixing bugs reported by the community.



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
  • 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
  • 20+ notification platforms: Netdata's health watchdog sends warning and critical alarms to your favorite
    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

💡 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

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
and anonymous

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

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
, including
Kubernetes, .deb/.rpm
, 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.


You can find most of the Netdata team in our community forum. It's the best place to
ask questions, find resources, and get to know the Netdata team.

You can also find Netdata on:


We welcome contributions to our code and to our
documentation. Feel free to join the team!

To report bugs or get help, use GitHub's issues.

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

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

So, we follow the tradition...