Hi,
We kindly request to review the following information and provide instructions for the next steps.
We will be honored to be part of CNCF.
Thank you!
netdata
Name of project: netdata
netdata description
netdata is an open source, distributed performance and health monitoring system. At its core is a highly optimized, lightweight monitoring agent that is installed on all systems (physical servers, container hosts, container guests, VM hosts, VM guests, IoT).
A netdata running at a VM or container host (or a privileged container guest) can monitor all the VMs and containers of the system using cgroups
. But netdata may also be installed inside containers or VMs to monitor just them.
netdata is distributed in nature, attempting to eliminate most of the centralized functions in monitoring. Each netdata installation is (by default) autonomous, providing all monitoring functions by itself (data collection, metrics database, web API for querying the database, visualization, health monitoring and notifications). Complex hierarchies of netdata servers are also supported (autonomous, headless collectors, headless proxies, store and forward proxies, database masters).
Each netdata node supports metrics archiving to industry standard time-series dbs (prometheus, graphite, opentsdb and all compatible ones - these are only used for archiving - netdata does not need these servers and never reads the metrics back). This means netdata can also be used as a data collector for other monitoring solutions.
netdata key differentiations are:
- per second data collection of all metrics, using just 1% CPU of a single core (the netdata core is a multithreaded lockless daemon, written in C, highly optimized to adapt to the system it runs). netdata metrics resolution can only be compared with console tools.
- fast, really fast, its API responds to all queries in less than 1 ms, providing sub-second latency between collection and visualization.
- highly interactive visualization, using carefully selected, adapted and integrated javascript libraries netdata provides speedy and snazzy dashboards for monitoring and evaluating the performance of the system and its applications.
- autodetection of all metrics, out of the box, netdata collects more that 5000 distinct metrics, most of which support auto-detection, offering virtually zero configuration installations.
- sophisticated health monitoring, it also comes with a few hundred alarms pre-configured for detecting common system and application issues and supports industry standard notification methods (email, syslog, slack, pagerduty, twilio, pushover, irc channels, messagebird, pushbullet, discord, alerta, flock, telegram, etc)
- open and embeddable, a) netdata has a plugin architecture for data collection supporting any language using stdout for metrics collection, b) netdata is a very fast, fully featured, statsd server, c) interactive netdata charts can be embedded on any web page by just adding a
div
element (without writing javascript). For example netdata charts can be embedded on Atlassian's Confluence pages.
- meaningful, netdata organizes metrics into collections with appropriate meaning, context and scope, making monitoring and performance troubleshooting a lot more effective (the default netdata dashboards are also optimized for quickly spotting anomalies). Furthermore, this structure allows netdata to be used as an educational tool for understanding and learning the underlying monitored technologies.
- secure by design, the design of netdata allows using it in the most demanding setups, including PCI Level 1 certified environments. netdata runs in userspace, unprivileged (there are a few exceptions for plugins that can only collect data when running with escalated privileges - netdata isolates these plugins). netdata does not directly expose any of the collected data on the wire. The only data exposed are processed metric data and related metadata (everything that is visible on the netdata dashboards). Furthermore, all communication between netdata components is unidirectional (slave->master, plugin->server), so that plugins and slaves cannot be manipulated from the outside.
netdata currently runs on Linux, FreeBSD and MacOS.
It was first released in Mar 30, 2016.
You can also have an overview of its internals, with this infographic (click it, it is interactive):
![netdata-overview](https://user-images.githubusercontent.com/2662304/37909754-6c812a7c-3114-11e8-8673-0d1926a9793a.png)
netdata community
home page: https://my-netdata.io
github repo: https://github.com/firehol/netdata
metric |
snapshot |
live |
Github Watchers |
1.2k |
![](https://camo.githubusercontent.com/e800018f16474f1ff7f01a0b2c47adc8ac23bbee7fa7edded5f1d2aca4632810/68747470733a2f2f696d672e736869656c64732e696f2f6769746875622f77617463686572732f66697265686f6c2f6e6574646174612e7376673f7374796c653d666c6174266c6162656c3d4769746875622532305761746368657273) |
Github Stars |
30k |
![](https://camo.githubusercontent.com/5b0592d4218e62fa5ba36c1b9931774883468caa2d130365cde8284e42f3cafa/68747470733a2f2f696d672e736869656c64732e696f2f6769746875622f73746172732f66697265686f6c2f6e6574646174612e7376673f7374796c653d666c6174266c6162656c3d4769746875622532305374617273) |
Github Forks |
2.5k |
![](https://camo.githubusercontent.com/402e5ef58d6153250289ff9cc2b4aee93d83c2f9ad474955eb0a8e77911cbcdc/68747470733a2f2f696d672e736869656c64732e696f2f6769746875622f666f726b732f66697265686f6c2f6e6574646174612e7376673f7374796c653d666c6174266c6162656c3d476974687562253230466f726b73) |
Contributors |
163 |
![](https://camo.githubusercontent.com/117930840ccc9376435915a1385993304870357874b6066bac4195ebfffeb59d/68747470733a2f2f696d672e736869656c64732e696f2f6769746875622f636f6e7472696275746f72732f66697265686f6c2f6e6574646174612e7376673f7374796c653d666c6174266c6162656c3d436f6e7472696275746f7273) |
Docker Hub Pulls |
15M |
![Docker titpetric/netdata Pulls](https://camo.githubusercontent.com/addd946221324a8052daeb9f6137b30897dcad6353bda9c9ee0cf4c7ab86253b/68747470733a2f2f696d672e736869656c64732e696f2f646f636b65722f70756c6c732f7469747065747269632f6e6574646174612e7376673f6c6162656c3d646f636b657225323070756c6c732532307469747065747269632f6e657464617461)
![Docker firehol/netdata Pulls](https://camo.githubusercontent.com/e2b7cb7588f8dffcfaf7ab4bc5c5f0d2000b62bb2ddc7eb0c74403a2b8e218a0/68747470733a2f2f696d672e736869656c64732e696f2f646f636b65722f70756c6c732f66697265686f6c2f6e6574646174612e7376673f6c6162656c3d646f636b657225323070756c6c7325323066697265686f6c2f6e657464617461) |
twitter: https://twitter.com/linuxnetdata, followers: 1.8k
facebook page: https://www.facebook.com/linuxnetdata/, likes: 800, followers: 850
Usage statistics
Since May 16th 2016 (the date the global public netdata registry was released):
![Sessions Served](https://camo.githubusercontent.com/7a3f2cd97e9dc5ce97ce327077c1ff542b6de41b23c2db847b70bf010b52b6cd/68747470733a2f2f72656769737472792e6d792d6e6574646174612e696f2f6170692f76312f62616467652e7376673f63686172743d6e6574646174612e72656769737472795f73657373696f6e73266c6162656c3d73657373696f6e7325323073657276656426756e6974733d6e756c6c2676616c75655f636f6c6f723d79656c6c6f77677265656e26707265636973696f6e3d3026763432)
in the last 24 hours:
![Sessions Today](https://camo.githubusercontent.com/b73c349e6a86a8a0e61dbc9ae3e0320df0973e7bf66e9902c087f87fb1360913/68747470733a2f2f72656769737472792e6d792d6e6574646174612e696f2f6170692f76312f62616467652e7376673f63686172743d6e6574646174612e72656769737472795f73657373696f6e732661667465723d2d38363430302667726f75703d696e6372656d656e74616c2d73756d266f7074696f6e733d756e616c69676e6564266c6162656c3d73657373696f6e73253230736572766564253230746f64617926756e6974733d6e756c6c2676616c75655f636f6c6f723d79656c6c6f77677265656e26707265636973696f6e3d3026763432)
Keep in mind the above usage statistics reflect a (probably) small part of the netdata community, counting only those using the public netdata registry. Every netdata can be a netdata registry too, so most enterprise users configure their own.
netdata license
netdata is distributed under GPLv3+.
netdata external dependencies
netdata redistributes a number of third party libraries and tools. The full list, including their licenses, can be found here: https://github.com/firehol/netdata/blob/master/REDISTRIBUTED.md
To compile the netdata daemon only 2 libraries are needed:
zlib
libuuid
We also provide statically built packages (x64, alpine muslc), that can be installed on any system that does not have these dependencies (these packages require only a Linux kernel, so they can run even on systems with no package management).
Plugins may depend on third party libraries (for example, python plugins need python installed, although we provide key python dependencies so that the core python plugins will work on any version of python).
Source control
Github - https://github.com/firehol/netdata
Initial committers
netdata currently has several maintainers and key contributors for its core functions. The full list can be found at the repo contributors page.
The key contributors so far are:
- @l2isbad, core python dev, currently working on Go plugins too
- @paulfantom, was the core python dev a year ago, now working on other projects
- @Ferroin, many python plugins and a lot more work on various aspects of netdata
- @ccremer, contributed many python plugins to netdata
- @facetoe, postgres plugins and more
- @simonnagl, working on java plugins
- @philwhineray, packaging and CI automation
- @alonbl, autotools
- @vlvkobal, ported netdata to FreeBSD and MacOS, occasionally working on netdata
- @titpetric, dockerization of netdata
netdata has several packaging maintainers for integrating netdata to distributions. The full list can be found at this github issue.
Release methodology
We only merge stable and tested code to the official netdata repo. Once every a few months we release a new version (10 releases so far). Check the repo releases page for more information.
Communication channels
Github issues.
Documentation
Currently hosted on a gihub wiki. We need to work a lot more on documentation - currently it lacks uniformity and several parts of it are missing or are not adequate for general use.
The founder sponsored documentation rewrite, but there has not been much progress, so we need to find another solution.
Existing sponsorship
netdata received several sponsorships (mainly hosting and SaaS). You can find the full list at the netdata donations page.
The only direct cost is DNS registration, which is covered by the founder.
Statement on alignment with CNCF mission
netdata is the definition of cloud native monitoring. It is distributed by nature, eliminating most centralized components, lightweight to be used for monitoring containers and microservices, open and flexible enough to be integrated with any system and application, both for data collection (netdata is also a statsd server), but also for visualization and real-time health monitoring.
netdata is a mature, secure and stable application, that is used in production environments all over the world, and it has a track record of community acceptance.
What netdata is looking for
We believe that being part of CNCF:
- gives users a clear signal that netdata has its place in modern infrastructure stacks.
- will increase exposure and adoption of netdata.
We also hope that CNCF will help us:
- direct netdata development is areas that are critical for the modern infrastructure.
- find our way through open-source licensing, trademarking, etc. providing legal advice and help.