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-node processing 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!