Netdata v2.3.2 is a patch release to address issues discovered since v2.3.1.

This patch release provides the following bug fixes and updates:

• Fixed journal file creation reliability with improved error handling and simplified allocation process (#20018, @ktsaou)
• Fixed leakage of build environment identifiers by blacklisting GitHub runner machine IDs (#20016, @ktsaou)
• Fixed potential memory access violations by adding validation for journal file headers and page boundaries (#20013, @stelfrag)
• Fixed a rare crash condition by properly reinitializing data collection for obsolete or archived dimensions (#20007, @ktsaou)
• Fixed MegaCLI collector to properly handle missing battery backup units (#20008, @ilyam8)
• Changed UUID generation to use version 4 format for better uniqueness (#20002, @ktsaou)
• Added detection for additional CI environment variables to automatically disable telemetry (#19999, @ktsaou)
• Fixed Agent status system to handle null UUIDs and improved tracking of shutdown time, crash counts, and connection states (#19996, #20003, #20011 @ktsaou)
• Added detailed worker thread status information and enhanced crash diagnostics capabilities (#19992, @ktsaou)
• Fixed potential crash in Windows perflib collector when handling null pointers (#19985, @ktsaou)
• Fixed error reporting to preserve errno values during out-of-memory conditions (#19984, @ktsaou)
• Fixed potential crashes when handling empty data arrays (#19983, @ktsaou)
• Fixed Agent shutdown by properly joining ACLK and metadata threads before closing database connections (#19980, @stelfrag)
• Fixed random crashes during shutdown by avoiding precompiled database statements for host metadata (#19978, @stelfrag)
• Limited maximum database file size to 1GB to optimize memory usage during file operations (#19977, @stelfrag)
• Fixed crash in variable lookup function when processing search results with scores (#19972, @ktsaou)
• Fixed ACLK synchronization thread shutdown with better termination sequence and timeout handling for stuck operations (#19966, @stelfrag)
• Improved Parent node startup performance by preloading UUIDs into metrics registry for faster initialization (#19964, @ktsaou)
• Fixed Windows installer to properly manage configuration files and handle upgrades correctly (#19962, @thiagoftsm)
• Fixed potential crash in health alarm cleanup when unlinking alerts from charts (#19956, @stelfrag)
• Fixed buffer overflow when processing cloud rooms during Agent claiming on startup (#19954, @stelfrag)
• Updated Agent status reporting system with enhanced crash diagnostics, anonymized stack traces, and ACLK connection status tracking (#19953, #19957, #19959 @ktsaou)
• Fixed thread creation issues by adding retry logic when system resource limits are temporarily reached (#19951, @stelfrag)
• Added monitoring of IIS Application Pool metrics to Windows collector (#19950, @thiagoftsm)
• Improved metadata thread stability with better shutdown handling and enhanced event loop management (#19929, @stelfrag)
• Fixed potential deadlocks by processing alert configuration database operations asynchronously through the metadata thread (#19885, @stelfrag)
• Reworked shared memory management in eBPF plugin for more reliable interprocess communication (#19844, @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!