Go to file
Austin S. Hemmelgarn be980fd137
Fixed condition controlling use of static LWS in RPM builds. (#10661)
The original intent was to only use a static copy of LWS if we couldn’t
use a system copy. Due to two incorrect conditionals in the spec file
though, what was actually happening was that we were using a static
build of LWS on systems where we could use a system copy, and not
linking against LWS at all on other systems.

This fixes those conditionals so that we use a system copy if available,
and provide a static copy if a system copy is not available.
2021-02-22 07:09:40 -05:00
.github Fixed handling of Docker image tags for release builds. (#10615) 2021-02-08 11:10:47 -05:00
.travis Fixed argument handling in `.travis/trigger_docker_build.sh`. (#10546) 2021-01-22 09:35:04 -05:00
aclk Add ACLK proxy setting as host label (#10619) 2021-02-11 14:57:01 +01:00
backends Spelling md (#10508) 2021-01-18 07:43:43 -05:00
build Added support for using `/etc/cron.d` for auto-updates. (#9598) 2020-09-15 07:40:05 -04:00
build_external Spelling md (#10508) 2021-01-18 07:43:43 -05:00
claim Update claiming docs for Docker containers. (#10570) 2021-02-10 13:49:43 -05:00
cli Docs housekeeping for SEO and syntax, part 1 (#10388) 2021-01-07 11:44:43 -07:00
collectors Fix broken links in docs and add collectors to list (#10651) 2021-02-19 07:38:16 -07:00
contrib Fixed bundling of libwebsockets in binary packages. (#10460) 2021-01-11 08:21:22 -05:00
daemon fix container/host detection in system-info script (#10647) 2021-02-16 19:29:27 +03:00
database Add ACLK proxy setting as host label (#10619) 2021-02-11 14:57:01 +01:00
diagrams Docs housekeeping for SEO and syntax, part 1 (#10388) 2021-01-07 11:44:43 -07:00
docs Fix broken links in docs and add collectors to list (#10651) 2021-02-19 07:38:16 -07:00
exporting Fix prometheus remote write header (#10560) 2021-01-27 15:46:58 +02:00
health Fix broken links in docs and add collectors to list (#10651) 2021-02-19 07:38:16 -07:00
libnetdata Fix broken links in docs and add collectors to list (#10651) 2021-02-19 07:38:16 -07:00
packaging [ci skip] create nightly packages and update changelog 2021-02-22 00:49:48 +00:00
parser Spelling md (#10508) 2021-01-18 07:43:43 -05:00
registry Docs housekeeping for SEO and syntax, part 1 (#10388) 2021-01-07 11:44:43 -07:00
spawn Make libnetdata headers compilable by C++. (#10185) 2020-11-07 00:10:50 +00:00
streaming add `_is_k8s_node` label to the host labels (#10501) 2021-01-18 07:44:14 -05:00
system Fix systemd comment syntax (#10066) 2020-10-14 07:44:28 -04:00
tests Docs housekeeping for SEO and syntax, part 1 (#10388) 2021-01-07 11:44:43 -07:00
web Fix the context filtering on the data query endpoint (#10652) 2021-02-17 21:13:38 +02:00
.clang-format Add clang-format. Update Contribution guidelines. (#6677) 2019-09-20 16:44:20 +02:00
.codacy.yml Improving the ACLK performance - initial changes (#8399) 2020-03-14 07:35:49 +01:00
.codeclimate.yml modularized all source code (#4391) 2018-10-15 23:16:42 +03:00
.csslintrc added codeclimate coverage 2017-01-06 18:01:57 +02:00
.dockerignore Adds Docker based build system for Binary Packages, CI/CD, Smoke Testing and Development. (#7735) 2020-01-28 05:51:18 +10:00
.eslintignore added codeclimate coverage 2017-01-06 18:01:57 +02:00
.eslintrc added codeclimate coverage 2017-01-06 18:01:57 +02:00
.gitattributes Add a .gitattributes file (#6381) 2019-07-05 11:54:32 +02:00
.gitignore Move ACLK Legacy into a subfolder (#10265) 2021-01-19 09:41:35 +01:00
.lgtm.yml Split js 2 (#4581) 2018-11-08 11:37:06 +02:00
.mlc_config.json GitHub action markdown link check update (#10474) 2021-01-11 13:50:16 -05:00
.remarkignore add CHANGELOG.md to .remarkignore (#6671) 2019-08-15 16:41:08 -07:00
.remarkrc.js Change lint standard for lists (#10371) 2021-01-07 08:43:18 -07:00
.squash.yml Squash integration (#5566) 2019-09-16 16:49:31 +02:00
.travis.yml Fixed handling of Docker image tags for release builds. (#10615) 2021-02-08 11:10:47 -05:00
.yamllint.yml github/workflow: disable `document-start` yamllint check (#8522) 2020-05-06 20:41:26 +03:00
BREAKING_CHANGES.md Docs housekeeping for SEO and syntax, part 1 (#10388) 2021-01-07 11:44:43 -07:00
BUILD.md Spelling md (#10508) 2021-01-18 07:43:43 -05:00
CHANGELOG.md [ci skip] create nightly packages and update changelog 2021-02-22 00:49:48 +00:00
CMakeLists.txt Move ACLK Legacy into a subfolder (#10265) 2021-01-19 09:41:35 +01:00
CODE_OF_CONDUCT.md Docs housekeeping for SEO and syntax, part 1 (#10388) 2021-01-07 11:44:43 -07:00
CONTRIBUTING.md Updated contributing guidelines to suggest use of Draft PRs. (#10125) 2020-11-30 07:03:47 -05:00
CONTRIBUTORS.md web/gui: Added support for per series styling for dygraphs (#8668) 2021-01-04 13:10:20 +01:00
Dockerfile Remove the confusion around the multiple Dockerfile(s) we have (#8214) 2020-03-10 08:12:26 +10:00
Dockerfile.test Remove the confusion around the multiple Dockerfile(s) we have (#8214) 2020-03-10 08:12:26 +10:00
HISTORICAL_CHANGELOG.md Spelling md (#10508) 2021-01-18 07:43:43 -05:00
LICENSE remove license templates; add info about SPDX to main license file 2018-09-08 15:53:07 +02:00
Makefile.am Move ACLK Legacy into a subfolder (#10265) 2021-01-19 09:41:35 +01:00
README.md Update latest release on main README (#10590) 2021-02-03 12:03:02 -07:00
REDISTRIBUTED.md Docs housekeeping for SEO and syntax, part 1 (#10388) 2021-01-07 11:44:43 -07:00
SECURITY.md Docs housekeeping for SEO and syntax, part 1 (#10388) 2021-01-07 11:44:43 -07:00
build-artifacts.sh Fix the netdata-updater.sh to correctly pass REINSTALL_OPTIONS (finally) (#8808) 2020-08-25 15:25:26 +10:00
configs.signatures Drop dirty dbengine pages if disk cannot keep up (#7777) 2020-02-06 21:58:13 +02:00
configure.ac Move ACLK Legacy into a subfolder (#10265) 2021-01-19 09:41:35 +01:00
coverity-scan.sh Fix coverity scan (#8388) 2020-03-13 07:24:06 +10:00
cppcheck.sh optimized ses and added des (#4470) 2018-10-24 03:03:57 +03:00
netdata-installer.sh New eBPF kernel (#10434) 2021-01-13 15:02:20 +00:00
netdata.cppcheck remove static dir config 2018-09-08 15:45:34 +02:00
netdata.spec.in Fixed condition controlling use of static LWS in RPM builds. (#10661) 2021-02-22 07:09:40 -05:00
package-lock.json fix minor vulnerability alert, updating socket-io dependency (#10557) 2021-01-27 16:50:16 +01:00
package.json fix minor vulnerability alert, updating socket-io dependency (#10557) 2021-01-27 16:50:16 +01:00

README.md

Netdata

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

Menu

Features

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 https://my-netdata.io/kickstart.sh)

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

Docker

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 http://localhost:19999, or http://NODE:19999.

Other operating systems

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

Post-installation

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.

Infographic

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

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.

Community

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:

Contribute

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.

License

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

Is it any good?

Yes.

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