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.
 
 
 
 
 
 
Givou 7c45b5e0ea „Makefile.am“ ändern 11 months ago
.github fix bug_report.md syntax error (#10269) 11 months ago
.travis „Makefile.am“ ändern 11 months ago
aclk adds child query support to ACLK (#10030) 11 months ago
backends „Makefile.am“ ändern 11 months ago
build „Makefile.am“ ändern 11 months ago
build_external Change streaming terminology to parent/child in docs (#9312) 1 year ago
claim ACLK Child Availability Messages (#9918) 11 months ago
cli Docs: Standardize links between documentation (#8638) 2 years ago
collectors Add optional info on how to also add some default alarms as part of submitting a collector. (#10302) 11 months ago
contrib „Makefile.am“ ändern 11 months ago
daemon Add guide: How to optimize Netdata's performance (#10271) 11 months ago
database Fix race condition in rrdset_first_entry_t() and rrdset_last_entry_t() (#10276) 11 months ago
diagrams Bulk add frontmatter to all documentation (#8354) 2 years ago
docs Add guide: How to optimize Netdata's performance (#10271) 11 months ago
exporting Fix compilation with https disabled. Fixes #10278 (#10279) 11 months ago
health Fix race condition in rrdset_first_entry_t() and rrdset_last_entry_t() (#10276) 11 months ago
libnetdata Migrate metadata log to SQLite (#10139) 11 months ago
packaging [ci skip] create nightly packages and update changelog 11 months ago
parser „Makefile.am“ ändern 11 months ago
registry Make libnetdata headers compilable by C++. (#10185) 12 months ago
spawn Make libnetdata headers compilable by C++. (#10185) 12 months ago
streaming Add guide: How to optimize Netdata's performance (#10271) 11 months ago
system Fix systemd comment syntax (#10066) 1 year ago
tests Correctly fix handling of CI Slack notifications. (#9902) 1 year ago
web Alarms collector (#10042) 11 months ago
.clang-format Add clang-format. Update Contribution guidelines. (#6677) 2 years ago
.codacy.yml Improving the ACLK performance - initial changes (#8399) 2 years ago
.codeclimate.yml modularized all source code (#4391) 3 years ago
.csslintrc added codeclimate coverage 5 years ago
.dockerignore Adds Docker based build system for Binary Packages, CI/CD, Smoke Testing and Development. (#7735) 2 years ago
.eslintignore added codeclimate coverage 5 years ago
.eslintrc added codeclimate coverage 5 years ago
.gitattributes Add a .gitattributes file (#6381) 2 years ago
.gitignore Add HTTP and HTTPS support to the simple exporting connector (#9911) 12 months ago
.lgtm.yml Split js 2 (#4581) 3 years ago
.mlc_config.json Fix Docs GitHub Action with ignore list and update (#10002) 11 months ago
.remarkignore add CHANGELOG.md to .remarkignore (#6671) 2 years ago
.remarkrc.js address lgtm alerts (#7441) 2 years ago
.squash.yml Squash integration (#5566) 2 years ago
.travis.yml Removed lifecycle checks from Travis CI. (#10305) 11 months ago
.yamllint.yml github/workflow: disable `document-start` yamllint check (#8522) 1 year ago
BREAKING_CHANGES.md Bulk add frontmatter to all documentation (#8354) 2 years ago
BUILD.md Bulk add frontmatter to all documentation (#8354) 2 years ago
CHANGELOG.md [ci skip] create nightly packages and update changelog 11 months ago
CMakeLists.txt Migrate metadata log to SQLite (#10139) 11 months ago
CODE_OF_CONDUCT.md Update CoC and widen scope to community (#10186) 12 months ago
CONTRIBUTING.md Updated contributing guidelines to suggest use of Draft PRs. (#10125) 11 months ago
CONTRIBUTORS.md Fix print message when building for Ubuntu Focal (#9694) 1 year ago
Dockerfile Remove the confusion around the multiple Dockerfile(s) we have (#8214) 2 years ago
Dockerfile.test Remove the confusion around the multiple Dockerfile(s) we have (#8214) 2 years ago
HISTORICAL_CHANGELOG.md multiple files: fix typos (#7752) 2 years ago
LICENSE remove license templates; add info about SPDX to main license file 3 years ago
Makefile.am „Makefile.am“ ändern 11 months ago
README.md Update README.md (#10146) 1 year ago
REDISTRIBUTED.md python.d: add job file lock registry (#9564) 1 year ago
SECURITY.md Correct vulnerability reporting instructions (#9696) 1 year ago
build-artifacts.sh Fix the netdata-updater.sh to correctly pass REINSTALL_OPTIONS (finally) (#8808) 1 year ago
configs.signatures Drop dirty dbengine pages if disk cannot keep up (#7777) 2 years ago
configure.ac Migrate metadata log to SQLite (#10139) 11 months ago
coverity-scan.sh Fix coverity scan (#8388) 2 years ago
cppcheck.sh optimized ses and added des (#4470) 3 years ago
netdata-installer.sh Fixed two bugs related to version handling in install and update code. (#10162) 12 months ago
netdata.cppcheck remove static dir config 3 years ago
netdata.spec.in Use automatic dependency generation for RPM builds. (#9937) 1 year ago
package-lock.json dashboard v1.0.26 (#9639) 1 year ago
package.json fix minimist vulnerability (#8537) 2 years ago

README.md

Netdata

The best monitoring and troubleshooting for systems, containers, applications, and infrastructure.
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.

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

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. Then, see our documentation for the full picture.

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