netdata

May 16th, 2016

netdata v1.2.0 released!

30% faster!

netdata registry, the first step towards scaling out performance monitoring!

real-time Linux Containers monitoring!

dozens of additional new features, optimizations, bug-fixes

May 1st, 2016

320.000+ views, 92.000+ visitors, 28.500+ downloads, 11.000+ github stars, 700+ forks, 1 month!

And it still runs with 600+ git downloads... per day!

Check what our users say about netdata.

Real-time performance monitoring, done right!

This is the default dashboard of netdata:

real-time, per second updates, snappy refreshes!
300+ charts out of the box, 2000+ metrics monitored!
zero configuration, zero maintenance, zero dependencies!

Live demo: http://netdata.firehol.org

Features

netdata is a highly optimized Linux daemon providing real-time performance monitoring for Linux systems, Applications, SNMP devices, over the web!

It tries to visualize the truth of now, in its greatest detail, so that you can get insights of what is happening now and what just happened, on your systems and applications.

This is what you get:

Stunning bootstrap dashboards, out of the box (themable: dark, light)
Blazingly fast and super efficient, mostly written in C (for default installations, expect just 2% of a single core CPU usage and a few MB of RAM)
Zero configuration - you just install it and it autodetects everything
Zero dependencies, it is its own web server for its static web files and its web API
Zero maintenance, you just run it, it does the rest
Custom dashboards that can be built using simple HTML (no javascript necessary)
Extensible, you can monitor anything you can get a metric for, using its Plugin API (anything can be a netdata plugin - from BASH to node.js, so you can easily monitor any application, any API)
Embeddable, it can run anywhere a Linux kernel runs and its charts can be embedded on your web pages too

What does it monitor?

This is what it currently monitors (most with zero configuration):

CPU usage, interrupts, softirqs and frequency (total and per core)
RAM, swap and kernel memory usage (including KSM and kernel memory deduper)
Disks (per disk: I/O, operations, backlog, utilization, space, etc)
Network interfaces (per interface: bandwidth, packets, errors, drops, etc)
IPv4 networking (bandwidth, packets, errors, fragments, tcp: connections, packets, errors, handshake, udp: packets, errors, broadcast: bandwidth, packets, multicast: bandwidth, packets)
IPv6 networking (bandwidth, packets, errors, fragments, ECT, udp: packets, errors, udplite: packets, errors, broadcast: bandwidth, multicast: bandwidth, packets, icmp: messages, errors, echos, router, neighbor, MLDv2, group membership, break down by type)
netfilter / iptables Linux firewall (connections, connection tracker events, errors, etc)
Linux DDoS protection (SYNPROXY metrics)
Processes (running, blocked, forks, active, etc)
Entropy (random numbers pool, using in cryptography)
NFS file servers, v2, v3, v4 (I/O, cache, read ahead, RPC calls)
Network QoS (yes, the only tool that visualizes network tc classes in realtime)
Linux Control Groups (containers), systemd, lxc, docker, etc
Applications, by grouping the process tree (CPU, memory, disk reads, disk writes, swap, threads, pipes, sockets, etc)
Users and User Groups resource usage, by summarizing the process tree per user and group (CPU, memory, disk reads, disk writes, swap, threads, pipes, sockets, etc)
Apache web server mod-status (v2.2, v2.4) and cache log statistics (multiple servers)
Nginx web server stub-status (multiple servers)
mySQL databases (multiple servers, each showing: bandwidth, queries/s, handlers, locks, issues, tmp operations, connections, binlog metrics, threads, innodb metrics, etc)
Redis databases (multiple servers, each showing: operations, hit rate, memory, keys, clients, slaves)
memcached databases (multiple servers, each showing: bandwidth, connections, items, etc)
ISC Bind name server (multiple servers, each showing: clients, requests, queries, updates, failures and several per view metrics)
Postfix email server message queue (entries, size)
exim email server message queue (emails queued)
IPFS (Bandwidth, Peers)
Squid proxy server (multiple servers, each showing: clients bandwidth and requests, servers bandwidth and requests)
Hardware sensors (temperature, voltage, fans, power, humidity, etc)
NUT UPSes (load, charge, battery voltage, temperature, utility metrics, output metrics)
Tomcat (accesses, threads, free memory, volume)
PHP-FPM (multiple instances, each reporting connections, requests, performance)
hddtemp (disk temperatures)
SNMP devices can be monitored too (although you will need to configure these)