Netdata v1.45.4 is a patch release to address issues discovered since v1.45.3.

This patch release provides the following bug fixes and updates:

• Added missing update_every property to the health prototype JSON schema (#17613, @ktsaou)
• Fixed issue where parent alerts remained active after child disconnection, by resetting health on child disconnect (#17612, @ktsaou)
• Fixed a packaging issue that prevented ndsudo from having the setuid bit in static builds (#17583, @ilyam8)
• Increased spawn server command size and added shutdown safeguard to prevent crashes from command size limit exceeded (#17566, @stelfrag)
• Fixed error code reporting for failed data insertion in SQLite (#17508, @stelfrag)
• Fixed issue with name-only label matching (#17482, @stelfrag)
• Improved Cloud connectivity: automatically re-establish connection upon system resume from suspension by scheduling a node update (#17444, @stelfrag)
• Improved termination handling: start watcher thread post-fork, preventing main process from waiting indefinitely on TERM signal (#17436, @stelfrag)
• Fixed priority order for alarms and alarm templates: now, alarms are applied before alarm templates consistently, regardless of their order in configuration files (#17398, @ktsaou)
• Added option for health table cleanup with 'netdata -W sqlite-alert-cleanup' command (#17385, @stelfrag)

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!