Releases: netdata/netdata
v2.2.6
Netdata v2.2.6 is a patch release to address issues discovered since v2.2.5.
This patch release provides the following bug fixes and updates:
- Fixed log2journal to properly handle empty JSON arrays and objects in log parsing (#19685, @ktsaou)
- Fixed MariaDB collector to handle CPU time values reported in microseconds since version 10.11.11 (#19683, @ilyam8)
- Added user action logging to dyncfg while ensuring sensitive information is hidden when dashboard is in anonymous mode (#19674, @ktsaou)
- Disabled legacy Go sensors collector in preparation for removal, as metrics are now collected by the C implementation (#19667, @ilyam8)
- Added user action logging to go.d.plugin dyncfg (#19666, #19672, #19673, #19676 @ilyam8)
- Added periodic event loop processing to prevent database engine starvation (#19661, @ktsaou)
- Added deployment metrics collection to KubeState collector, including replica status and availability alerts (#19657, #19662, #19664 @ilyam8)
- Added agent timezone information to host labels (#19656, @ktsaou)
- Added fallback to standard memory allocation when onewayalloc allocator fails (#19646, @ktsaou)
- Fixed Windows log collection to append new fields instead of renumbering them (#19640, @ktsaou)
- Improved error handling in Windows perflib collector to be more robust (#19631, @ktsaou)
- Prevented Sentry report flooding during database initialization failures (#19628, @ktsaou)
- Added a new alert to detect system reboots (#19624, @ilyam8)
- Fixed SSL certificate handling in statically linked libcurl by properly configuring certificate paths during build (#19622, @ktsaou)
- Added additional context information to Sentry crash reports for better debugging (#19608, @vkalintiris)
- Added automatic detection of system DNS servers from /etc/resolv.conf in DNS query collector (#19562, @ilyam8)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.2.5
Netdata v2.2.5 is a patch release to address issues discovered since v2.2.4.
This patch release provides the following bug fixes and updates:
- Fixed MariaDB collector to handle CPU time values reported in microseconds since version 11.4.5 (#19618, @ilyam8)
- Changed clickhouse_replicated_readonly_tables info to clarify read-only state conditions for replicated tables (#19616, @ilyam8)
- Fixed indirect cloud access to function properly when an Agent is claimed but temporarily offline by using Parent's claim ID (#19611, @ktsaou)
- Added data interpolation to median and percentile calculations in the stats.d plugin (#19606, @ktsaou)
- Fixed potential database access issues during shutdown by properly closing the database when startup errors occur (#19600, @stelfrag)
- Fixed a memory corruption issue by properly dequeuing contexts from hub before deletion (#19599, @ktsaou)
- Fixed various issues in journal watcher, including improved event parsing, corrected path handling, and resolved memory-related bugs (#19592, @ktsaou)
- Fixed NVMe device discovery to properly handle device paths in nvme-cli v2.11 (#19577, @ilyam8)
- Fixed MySQL collector to properly respect the global variables refresh interval instead of collecting them on every iteration (#19549, @arkamar)
- Fixed several CI/build system issues, including static build conditions, POWER8+ build hosts, Ubuntu runner versions, and compiler flags (#19575, #19579, #19614, #19619, @Ferroin)
- Fixed Amazon Linux aarch64 package builds by migrating to GitHub's ARM CI runners (#19427, @Ferroin)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.2.4
Netdata v2.2.4 is a patch release to address issues discovered since v2.2.3.
This patch release provides the following bug fixes and updates:
- Fixed go.d plugin to properly clean up charts for stopped and removed jobs to prevent stale alerts (#19573, @ilyam8)
- Fixed a memory leak in the health component (#19569, @stelfrag)
- Added a new agent status to indicate when connection to the Cloud is in progress (#19564, @stelfrag)
- Fixed Windows collector to properly monitor multiple MSSQL instances running simultaneously (#19559, @thiagoftsm)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.2.3
Netdata v2.2.3 is a patch release to address issues discovered since v2.2.2.
This patch release provides the following bug fixes and updates:
- Fixed an issue with newly created and claimed agents not immediately appearing in the cloud (#19542 @stelfrag)
- Fixed database engine to properly handle files larger than 4GB by correcting 32-bit variable limitations (#19538, #19539 @ktsaou)
- Fixed an issue where contexts remained in a non-live state after child reconnections due to incorrectly cached collection flags (#19536 @ktsaou)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.2.2
Netdata v2.2.2 is a patch release to address issues discovered since v2.2.1.
This patch release provides the following bug fixes and updates:
- Fixed a memory corruption issue that occurred when streaming remote functions failed (#19532 @ktsaou)
- Fixed detection of Microsoft SQL Server named instances in the Windows MSSQL collector (#19527 @thiagoftsm)
- Fixed an issue where receiver connections were terminated when sender encountered socket errors, while also optimizing data collection performance (#19524 @ktsaou)
- Simplified eBPF plugin dependencies by linking directly to libbpf instead of through libnetdata (#19514 @Ferroin)
- Removed unnecessary lm_sensors dependency from Go plugin in RPM packages (#19511 @k0ste)
- Fixed URL-encoded proxy credentials handling in ACLK to properly decode usernames and passwords containing special characters (#19508 @ktsaou)
- Fixed alert transition timing to use a 10-second delay for state changes to removed and to correctly use the alert trigger timestamp for cloud notifications (#19507 @stelfrag)
- Improved buildinfo output (-W buildinfo) to include additional plugins and compiler flag information for better troubleshooting support (#19506, #19513 @ktsaou)
- Fixed NVMe device discovery to support the new output format introduced in nvme-cli v2.11 (#19505 @ilyam8)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.2.1
Netdata v2.2.1 is a patch release to address issues discovered since v2.2.0.
This patch release provides the following bug fixes and updates:
- Fixed tables showing incorrect positive values for negative metrics (#19496, #19497 @ktsaou)
- Added
ifb4*to default network interface exclusion patterns of proc.plugin (#19494, @intelfx) - Removed obsolete ZFS pool state configuration option (#19491, @intelfx)
- Improved alert processing performance through optimized SQL operations and improved transition checksg (#19489, @stelfrag)
- Improved performance when compiled with LTO enabled (#19488, @ktsaou)
- Improved alert transition processing performance by using precompiled SQL statements (#19487, @stelfrag)
- Fixed issues identified by Coverity code analysis (#19484, @ktsaou)
- Added system information, Agent name and version to Netdata-streaming function (#19482, #19485 @ktsaou)
- Changed ping plugin's privileged option to true by default for dynamic configuration jobs (#19480, @ilyam8)
- Fixed high CPU usage in privileged ping collector by updating pro-bing library to 0.6.0 (#19477
- Improved performance by optimizing host status checks and ingestion status queries (#19472, @ktsaou)
- Improved stale node cleanup performance by moving
netdatacli remote-stale-nodeprocessing to a worker thread (#19471, @stelfrag) - Fixed a crash that occurred during virtual nodes cleanup when receiver is not present (#19467, @ktsaou)
- Fixed unnecessary health alerts by ensuring child nodes complete replication before initializing health checks (#19463, @stelfrag)
- Improved ACLK memory management by implementing ARAL allocator for command queuing (#19459, @stelfrag)
- Added Pulse metrics for parent node to improve stream health monitoring (#19445, #19466 @ktsaou)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.2.0
Table of Contents
Netdata Growth
- 1.5 million downloads per day
- 73k GitHub stars!
- 653M Docker Hub pulls!
Netdata continues to experience phenomenal growth, with over 1.5 million downloads daily through Cloudflare and Docker Hub, fueling observability for users worldwide.
Thanks to your unwavering support ❤️, Netdata is the leader in the observability category in the CNCF landscape, ahead of all other solutions including Elasticsearch, Grafana, and Prometheus in GitHub stars, showcasing the trust and admiration of our community.
This success is driving rapid adoption among enterprises, reflecting the growing recognition of Netdata as the go-to observability solution for both cloud-native and on-premises environments. Our commitment remains steadfast: to deliver cutting-edge, AI-powered observability with unmatched performance and simplicity—all while being significantly more affordable.
As we evolve, our focus on empowering businesses with higher-fidelity AI insights ensures Netdata remains the easiest and fastest way to optimize infrastructure and applications at any scale. 🚀
You like Netdata? Give Netdata a ⭐ too, on GitHub!
Release Summary
Netdata 2.2.0 delivers major performance optimizations targeting Parent-to-Parent streaming deployments, achieving 50% less memory usage across all installations, while Parent nodes streaming to other Parents benefit from 50% reduced bandwidth usage and 20% lower CPU utilization.
New auto-detected configuration profiles optimize performance for different use cases: Parent, Child, and IoT deployments.
Release Highlights
Performance and Scalability Improvements
| Area | Improvement | Technical Details |
|---|---|---|
| Memory Management | 50% reduction in memory usage (all deployments) | Eliminated majority of memory fragmentation by separating long-standing data from ephemeral data using specialized allocation algorithms. Enhanced out-of-memory protection allows cache shrinking to near-zero when needed, compatible with container and Kubernetes environments. |
| Network Efficiency | 50% reduction in bandwidth (Parent-to-Parent streaming) | Implemented message combining for multiple metric updates, enabling higher compression ratios and reduced network overhead through larger network frames when streaming between Parent nodes. |
| Processing Performance | 20% reduction in CPU usage (Parent-to-Parent streaming) | Improved lock contention with advanced algorithms, enhancing fairness, responsiveness, and scalability specifically for Parents streaming to other Parents. DBEngine cache now delivers full capacity at scale. |
| Startup Performance | Significantly faster startup | Parallelized metadata loading based on available CPU cores, resulting in significantly reduced loading times. |
| Configuration Management | New profile system | Introduced auto-detected configuration profiles: - Parent: Optimized for data transfer between parents. - Child: Minimized resource footprint. - IoT: Configured for minimum resource usage. |
| Cloud Connectivity | Enhanced reliability | Reworked code to ensure stable Netdata Cloud connectivity under heavy load conditions on busy Netdata Parents. |
Enhanced Single Node Dashboard View
Introducing an improved single-node dashboard experience! You can now open a dedicated dashboard for any node directly from the Nodes tab (or other locations), giving you instant access to all critical data related to that node.
The dashboard consolidates essential information into intuitive tabbed views, including:
- Metrics
- Top
- Logs
- Alerts
- Anomalies
- Events
With automatic data filtering specific to the selected node, you can navigate seamlessly between tabs to quickly access troubleshooting insights. When you're done, the entire dashboard can be closed effortlessly with a single click.
This streamlined experience makes monitoring and managing individual nodes easier and faster than ever before.
Personalized Space Navigation
Customizable Space Navigation
You can now personalize the order and appearance of your space icons in the left panel:
- Reorder Spaces: Simply drag and drop space icons to organize them in the order that works best for you.
- Customize Colors: Use the color picker to assign unique colors to your space icons, making them easily distinguishable.
- Save Preferences: Your customizations are saved automatically, ensuring a consistent experience every time you access your dashboard.
If you have multiple spaces, you can now find and access the spaces you are looking for much faster and more intuitively than before.
Acknowledgments
- @enoch85 for adding instructions for setting up email notifications for Docker Compose.
Contributions
Collectors
Improvements
- Add collector for optical transceiver modules (go.d/ethtool) (#19426, #19428,#19429, #19430, #19434 @ilyam8)
- Add support for Pod exclusion using
netdata.cloud/ignoreannotation (go.d/k8s_state) (#19342, @ilyam8) - Add container filtering via
netdata.cloud/ignorelabel (go.d/docker) (#19341, @ilyam8) - Add a configuration option to filter containers (go.d/docker) (#19337, #19339 @ilyam8)
- Add collector for YugabyteDB (go.d/yugabytedb) (#19325, @ilyam8)
- Add container filtering via
netdata.cloud/*labels (cgroups.plugin) (#19315, #19316, #19318 @ktsaou @ilyam8) - Add collector for NATS (go.d/nats) (#19252, #19253, #19262, #19264, #19266, #19280, #19282, #19284, #19285, #19303, #19309,#19311, @ilyam8)
- Port sensors collector from Go to C (debugfs/sensors) (#19251, #19294 [@ktsaou](https:...
Contributors
Assets 18
v2.1.1
Netdata v2.1.1 is a patch release to address issues discovered since v2.1.0.
This patch release provides the following bug fixes and updates:
- Fixed file descriptor leaks in the health subsystem (#19327, @ktsaou)
- Fixed netdata-updater.sh to use explicit paths for temporary directory creation instead of relying on TMPDIR environment variable (#19293, @ilyam8)
- Fixed netdata-updater.sh to correctly handle tmpdir-path argument regardless of other parameters (#19289, @ilyam8)
- Fixed cleanup of temporary files in netdata-updater.sh self-update process (#19288, @ilyam8)
- Fixed RabbitMQ collector to gracefully handle insufficient permissions when querying API definitions (#19277, @ilyam8)
- Fixed duplicate HELP and TYPE metadata in multi-node Prometheus exports (#19261, @ktsaou)
- Fixed crash in amdgpu collector when handling incomplete DRM data or sleeping graphics cards (#19258, @ktsaou)
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Make use of the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
v2.1.0
Table of Contents
Netdata Growth
- 1.5 million downloads per day
- 72.6k GitHub stars!
- 651M Docker Hub pulls!
Netdata continues to experience phenomenal growth, with over 1.5 million downloads daily through Cloudflare and Docker Hub, fueling observability for users worldwide.
Thanks to your unwavering support ❤️, Netdata is the leader in the observability category in the CNCF landscape, ahead of all other solutions, including Elasticsearch, Grafana, and Prometheus, in GitHub stars. This demonstrates the trust and admiration of our community.
This success drives rapid adoption among enterprises, reflecting the growing recognition of Netdata as the go-to observability solution for both cloud-native and on-premises environments. Our commitment remains steadfast: to deliver cutting-edge, AI-powered observability with unmatched performance and simplicity—all while being significantly more affordable.
As we evolve, our focus on empowering businesses with higher-fidelity AI insights ensures Netdata remains the easiest and fastest way to optimize infrastructure and applications at any scale. 🚀
You like Netdata? Give Netdata a ⭐ too, on GitHub!
Release Summary
This release focuses heavily on streaming functionality, enabling unprecedented scalability, reduced CPU overhead, and optimized memory utilization. Netdata has been re-architected to meet the demands of enterprise environments while maintaining its hallmark ease of use and affordability.
Release Summary
This release focuses heavily on streaming functionality, enabling unprecedented scalability, reduced CPU overhead, and optimized memory utilization. Netdata has been re-architected to meet the demands of enterprise environments while maintaining its hallmark ease of use and affordability.
Release Highlights
Major Performance and Scalability Improvements
This release significantly enhances Netdata's performance and streaming capabilities, with particular focus on multi-parent infrastructures:
- Optimized CPU Usage: Streamlined ML model distribution and improved thread management reduce CPU utilization by 30–50% in parent-child setups.
- Smarter Memory Management: New features prevent out-of-memory situations while maximizing cache usage for better query performance.
- Enhanced Multi-Parent Scalability: Improved load balancing and connection handling for more stable operation at scale.
- Optimized Query Processing: Prioritized handling of user queries ensures responsive experience even under heavy load.
Detailed Technical Improvements:
| Category | Feature | Benefit |
|---|---|---|
| CPU Optimization | ML Model Streaming | • ML models now stream between Netdata Agents alongside metric data • Options for edge or central ML training • 30-50% CPU reduction in parent-child setups • Note: Next major version will disable ML training on children by default |
| Thread Management | • Streaming threads fixed to match CPU cores • Single thread handles ingestion and re-streaming per node • Reduced context switches and cross-CPU communication |
|
| Memory Management | Out-of-Memory Protection | • Dynamic cache adjustment maintains 10% system memory buffer (max 5 GiB) • Container-aware (supports cgroups v1 and v2) • Configurable via [db].dbengine out of memory protection |
| Cache Optimization | • Option to utilize all available memory for caching • Reduced disk I/O on busy parent nodes • Enable with [db].dbengine use all ram for caches |
|
| ML Training Management | • Dynamic queue management prevents memory overload • Consistent performance during heavy ML workloads |
|
| Scalability | Parent Cluster Load Distribution | • Random parent selection for load distribution • Prevents single-node bottlenecks in large deployments |
| Connection Handling | • Randomized reconnection timing • Prevents connection floods • Smoother large-scale reconnect handling |
|
| Query Performance | Query Prioritization | • Immediate response to user queries under any load • Connection operations get secondary priority • Background tasks (replication, ML) yield to high-priority operations • Quick new node integration through expedited backfilling |
| Real-Time Response | • Responsive user experience during heavy processing • Efficient concurrent query handling • Maintains performance during high-load background operations |
Cloud: Automated Room Assignment with Label-Based Rules
Netdata Cloud Dashboard introduces node rule-based room assignment—a powerful new feature that transforms how you organize your infrastructure monitoring:
- Dynamic Room Assignment: Nodes are automatically placed into relevant rooms based on their host labels, eliminating manual organization.
- Rule-Based Management: Create flexible rules using host labels to define where nodes belong, ensuring consistent organization.
- Scale-Ready Architecture: As your infrastructure grows, new nodes are automatically sorted into appropriate rooms, maintaining clean monitoring structure.
Cloud: Configurable Alert Repeat Notifications
Netdata Cloud enhances alert management with customizable notification repeats:
- Custom Repeat Intervals: Set how often you want to be reminded about ongoing alerts for each notification channel.
- Automated Follow-ups: Receive automatic notification repeats for unresolved alerts based on your specified timeframe.
- Channel-Specific Settings: Configure different repeat frequencies for each integration to match your workflow.
Cloud: Pin Your Essential Charts with Dashboard Favorites
Netdata Cloud Dashboard introduces favorites pinning for faster access to your critical monitoring views:
- One-Click Pinning: Select and pin your most important charts and sections directly from the dashboard.
- Quick-Access Organization: Pinned items appear at the top of your Table of Contents for instant visibility.
Dynamic Configuration: Bulk Operations for Collectors and Alerts
Dynamic Configuration in Netdata now supports bulk operations on monitoring settings. You can perform the following operations on multiple collector jobs and health checks at once:
- Enable/Disable
- Restart
- Delete
Acknowledgments
- @orisano for removing a duplicated row in logging readme.
Contributions
Collectors
Contributors
Assets 18
v2.0.3
Netdata v2.0.3 is a patch release to address issues discovered since v2.0.2.
This patch release provides the following bug fixes and updates:
- Modified the Netdata service startup type to
Automatic (Delay Start)on Windows to enhance metric collection reliability after system reboots (#19063, @stelfrag).
Reinstalling Netdata should automatically configure the service to start with Windows using Automatic (Delayed Start).
If reinstalling didn't set this correctly, you can configure it manually:
- Open the Services Manager (Type "Services" in the Windows search bar).
- Find and right-click on the Netdata Agent service.
- Change the Startup type to Automatic (Delayed Start).
- Click Apply, then OK to save your changes.
Support options
As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels:
- Netdata Learn: Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata.
- GitHub Issues: Use the Netdata repository to report bugs or open a new feature request.
- GitHub Discussions: Join the conversation around the Netdata development process and be a part of it.
- Community Forums: Visit the Community Forums and contribute to the collaborative knowledge base.
- Discord Server: Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!