||11 months ago|
|.github||11 months ago|
|.travis||11 months ago|
|aclk||11 months ago|
|backends||11 months ago|
|build||11 months ago|
|build_external||1 year ago|
|claim||11 months ago|
|cli||2 years ago|
|collectors||11 months ago|
|contrib||11 months ago|
|daemon||11 months ago|
|database||11 months ago|
|diagrams||2 years ago|
|docs||11 months ago|
|exporting||11 months ago|
|health||11 months ago|
|libnetdata||11 months ago|
|packaging||11 months ago|
|parser||11 months ago|
|registry||12 months ago|
|spawn||12 months ago|
|streaming||11 months ago|
|system||1 year ago|
|tests||1 year ago|
|web||11 months ago|
|.clang-format||2 years ago|
|.codacy.yml||2 years ago|
|.codeclimate.yml||3 years ago|
|.csslintrc||5 years ago|
|.dockerignore||2 years ago|
|.eslintignore||5 years ago|
|.eslintrc||5 years ago|
|.gitattributes||2 years ago|
|.gitignore||12 months ago|
|.lgtm.yml||3 years ago|
|.mlc_config.json||11 months ago|
|.remarkignore||2 years ago|
|.remarkrc.js||2 years ago|
|.squash.yml||2 years ago|
|.travis.yml||11 months ago|
|.yamllint.yml||1 year ago|
|BREAKING_CHANGES.md||2 years ago|
|BUILD.md||2 years ago|
|CHANGELOG.md||11 months ago|
|CMakeLists.txt||11 months ago|
|CODE_OF_CONDUCT.md||12 months ago|
|CONTRIBUTING.md||11 months ago|
|CONTRIBUTORS.md||1 year ago|
|Dockerfile||2 years ago|
|Dockerfile.test||2 years ago|
|HISTORICAL_CHANGELOG.md||2 years ago|
|LICENSE||3 years ago|
|Makefile.am||11 months ago|
|README.md||1 year ago|
|REDISTRIBUTED.md||1 year ago|
|SECURITY.md||1 year ago|
|build-artifacts.sh||1 year ago|
|configs.signatures||2 years ago|
|configure.ac||11 months ago|
|coverity-scan.sh||2 years ago|
|cppcheck.sh||3 years ago|
|netdata-installer.sh||12 months ago|
|netdata.cppcheck||3 years ago|
|netdata.spec.in||1 year ago|
|package-lock.json||1 year ago|
|package.json||2 years ago|
The best monitoring and troubleshooting for systems, containers, applications, and infrastructure.
Preconfigured, opinionated, and always real-time.
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.
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
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...
Latest release: v1.26.0, October 14, 2020
The v1.26.0 release of the Netdata Agent brings exciting new collectors written in Go, a new integration with the DevOps startup StackPulse, and massive improvements to the way users navigate Netdata's documentation. We've also added compatibility with an exciting new feature that's coming soon to Netdata Cloud—stay tuned! This release contains 3 new collectors, 1 new notifcation method, 21 improvements, 13 documentation updates, and 12 bug fixes.
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
- 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.
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 https://my-netdata.io/kickstart.sh)
To view the Netdata dashboard, navigate to
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 \ netdata/netdata
To view the Netdata dashboard, navigate to
Other operating systems
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.
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.
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:
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.
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.".
So, we follow the tradition...