Netdata is distributed, real-time, performance and health monitoring for systems and applications. It is a highly optimized monitoring agent you install on all your systems and containers.
Netdata provides unparalleled insights, in real-time, of everything happening on the systems it runs (including web servers, databases, applications), using highly interactive web dashboards. It can run autonomously, without any third party components, or it can be integrated to existing monitoring tool chains (Prometheus, Graphite, OpenTSDB, Kafka, Grafana, etc).
Netdata is fast and efficient, designed to permanently run on all systems (physical & virtual servers, containers, IoT devices), without disrupting their core function.
Netdata is free, open-source software and it currently runs on Linux, FreeBSD, and MacOS.
The v1.25.0 release of the Netdata Agent is focused on improving Netdata’s usability across the board. We added more customization to how the Prometheus collector implemented in v1.24 meaningfully visualizes metrics. In addition, we’ve focused on fixing bugs and ensuring that core functionality of the Netdata Agent, such as the ACLK, works more efficiently.
This release contains 1 new collector, 27 improvements, 15 documentation updates, and 59 bug fixes.
At a glance
Improved filtering and grouping for the Prometheus collector gives you more flexibility in how Netdata collects and visualizes metrics from more than 600 Prometheus endpoints. The Prometheus collector is designed to visualize every metric exposed on a Prometheus endpoint generically, but one chart for every metric is often not the most meaningful presentation. Filtering and grouping options bring the same “bespoke” feeling that you find in our other collectors, such as having input/output metrics on a single chart instead of two.
You can read about filtering and grouping in our documentation right now. If you haven’t heard about the generic Prometheus collector, read our v1.24 blog post for details on why we continuously make Netdata more interoperable with other monitoring solutions.
We also made significant improvements to the robustness and responsiveness of the Agent-Cloud link (ACLK), which is used to stream metrics and alarm status if you sign up for Netdata Cloud and claim your nodes. The disconnect and reconnect process is now more reliable, and all metrics data is now Gzip compressed. Now that the payloads are smaller and more quickly processed, you’ll see improved responsiveness when viewing dashboards in Netdata Cloud.
We added a new Elasticsearch collector, written in Go, to help you collect metrics from and monitor Elasticsearch instances. This collector is preinstalled with the Netdata Agent and often works with zero configuration, but can also be tweaked to collect only specific stats, gather metrics with TLS, and more. See the documentation for generated charts and configuration options.