Netdata - v1.44.2

Netdata v1.44.2 is a patch release to address issues discovered since v1.44.1.

This patch release provides the following bug fixes and updates:

• Fixed an inconsistency where the NETDATA_LOG_LEVEL environment variable did not affect log level in Docker containers. (#16943, @ilyam8)
• Fixed inconsistent log severity across sources: log severity level setting now work for all Netdata log sources (daemon, collector, health, access, aclk). (#16922, @ilyam8)
• Fixed a bug in chartd.d.plugin that prevented loading of its modules configuration files. (#16939, @ilyam8)
• Fixed inaccurate server type identification in Netdata Cloud for FreeBSD jails. Jails are now recognized correctly. (#16858, @ilyam8)
• Fixed a bug that prevented the edit-config script from running correctly in Podman containers. The script now accurately identifies container environments. (#16825, @Ferroin)
• Fixed a bug that caused excessive logging of "Using host prefix directory" messages. (#16814, @ilyam8)
• Fixed incorrect label source for apps.plugin charts, ensuring they are now accessible when querying Prometheus metrics. (#16810, @boxjan)
• Fixed a bug in the cgroups.plugin that could lead to crashes. Additionally, addressed incorrect thread name during fatal Agent exits. (#16771, @ktsaou)
• Fixed a race condition related to pthread_detach() calls, preventing potential Netdata crashes during thread creation. (#16760, @ktsaou)
• Fixed a bug that caused "maximum number of cgroups reached" messages to spam logs. (#16730, @ilyam8)
• Fixed incorrect service file location during MacOS installation: now, launchctl commands can reliably start and stop Netdata. (#16693, @ilyam8)
• Fixed a bug that caused the Netdata claiming process to fail on macOS due to an inaccessible netdata-claim.sh script. (#16686, @ilyam8)
• Fixed missing host label streaming from child nodes: host labels are now transmitted reliably to parent nodes. (#16821, @stelfrag)
• Fixes a bug in clock resolution calculation that prevented some data collection plugins from working correctly. (#16720, @ktsaou)
• Fixed a bug that caused Netdata to crash when calculating database size due to missing or single datafiles. (#16699, @ktsaou)
• Fixed a bug that caused the cups.plugin to not terminate upon receiving a SIGPIPE (Broken Pipe) signal. (#16691, @ilyam8)
• Fixed a reference counting issue that could lead to Netdata crashes. (#16687, @ktsaou)
• Fixed charts context and family definitions of exporting engine. (#16683, @ilyam8)
• Fixed a bug that could cause crashes when processing web requests. (#16664, @ktsaou)
• Fixed improper handling of the dbengine event loop during shutdown. (#16658, @stelfrag)
• Fixed a potential memory corruption issue in database code. (#16654, @stelfrag)
• Fixed "response too big" error for Systemd-journal: addressed limitations by raising the maximum web response size. (#16649, @ktsaou)
• Fixed compilation issues with --disable-dbengine: addressed errors that prevented successful builds when this flag was used. (#16611, @stelfrag)
• Fixed labels corruption due to duplicate key/value pairs. Additionally, addressed logging errors that occurred during fatal Agent exits. (commit, @ktsaou)
• Update go.d.plugin to v0.58.0. (#16725, @ilyam8).

Acknowledgements

We would like to thank our dedicated, talented contributors who make up this amazing community. The time and expertise that you volunteer are essential to our success. We thank you and look forward to continuing to grow together to build a remarkable product.

• @boxjan for fixing incorrect label source for apps.plugin charts.

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 1900 engineers are already using it!