We're excited to announce the *scheduled stable release of rsyslog 8.2506.0 (aka 2025.06)*. This bi-monthly stable release serves as a snapshot of our continuous daily stable branch, catering to users who prefer a slower release cycle. It brings significant advancements in security integration, data processing, and our development infrastructure. ------------------------------ Key Technical Advancements in 8.2506.0
This release introduces several pivotal features and architectural improvements: - *Experimental omsendertrack Module:* This new output module is engineered to provide granular telemetry on message sender activity across all configured inputs. It periodically serializes sender statistics into a JSON object, enabling integration with downstream IT security and analytical systems that require insights into source behavior. While currently in an experimental proof-of-concept (PoC) phase, omsendertrack offers a foundational capability for enhanced security visibility and auditing. We anticipate further enhancements and expanded functionality based on practical deployment feedback. (Refer to: https://github.com/rsyslog/rsyslog/issues/5599) - *Advanced Lookup Table: Regex-Match Type:* We've augmented the lookup table functionality with a new table type supporting *regular expression-based matching*. This allows for partial string matches within lookup operations, providing a more flexible mechanism for data classification and transformation. While regex evaluations inherently carry a higher computational overhead compared to exact matches, this new type proves invaluable for use cases such as categorizing "noise" events or performing complex pattern-based lookups. - *Inception of AI-Augmented Development Workflows:* This release includes foundational changes to our project documentation, specifically the addition of AGENTS.md and updates to CONTRIBUTING.md. These revisions establish initial guidelines and protocols for integrating AI agents into the rsyslog development lifecycle. This strategic evolution aims to enhance development efficiency and code quality through supervised AI contributions, with strict adherence to auditability and maintainability standards. This marks the first step in our initiative to leverage AI for optimizing development and improving ease of use. - *Ongoing Containerization Efforts:* Several internal modifications and improvements in this release contribute to our ongoing initiative to containerize rsyslog. This effort aims to simplify deployment and management through Docker, offering a more portable and consistent operational environment. For more details on this strategic direction, please refer to: https://www.rsyslog.com/revitalizing-rsyslog-with-docker-a-new-era-of-log-management/?utm_source=rss&utm_medium=rss&utm_campaign=revitalizing-rsyslog-with-docker-a-new-era-of-log-management ------------------------------ Core Stability and Module Enhancements - *Core Fix: Hash Table Memory Initialization:* We addressed a critical bug where newly allocated memory segments during hash table expansion were not properly zero-initialized. This fix ensures data integrity and prevents potential instability during dynamic table growth. - *Queue Management: Diagnostic Reversion:* We reverted a previous commit (525a6f1bbf) that generated erroneous queue warning messages on startup. A correct implementation for enhanced queue diagnostics will be provided in a future release. - *TLS Subsystem: Improved Error Reporting:* Error messages for TLS accept failures are now enhanced to include remote peer information where discernible. This improvement significantly aids in diagnosing network connectivity and negotiation issues, particularly in environments with load balancers or health checks. - *imuxsock: Discarded Message Statistics:* A new counter has been introduced to track messages discarded by the imuxsock input module. This also corrects a bug where the submitted message count was incremented even for messages rejected due to rate limiting. - *omfwd: Regression Fix:* We corrected a regression that resulted in spurious "active target change" log messages due to an omitted check for actual state alteration. - *omazureeventhubs: Content-Type Correction:* We fixed an incorrect Content-Type definition during message encoding, ensuring proper communication with Azure Event Hubs. - *impstats: Prometheus Output Format:* The impstats module now supports output in Prometheus exposition format, facilitating direct ingestion by Prometheus scrapers or node_exporter via file scraping. - *omusrmsg: String Builder Safety:* We addressed a potential security vulnerability and build issue related to an unsafe string builder implementation. ------------------------------ Development Infrastructure Improvements - *CI: Python-Based Codestyle Checker:* We've integrated a new Python-based codestyle checker, replacing a less maintainable C-source solution. - *CI Workflow Enhancements:* General improvements have been made to our Continuous Integration (CI) workflows for increased efficiency and reliability. We recommend all users to upgrade to rsyslog 8.2506.0 to leverage these enhancements and benefit from the improved stability and functionality. For comprehensive details on all changes, please consult the full changelog on our GitHub repository <https://github.com/rsyslog/rsyslog/blob/master/ChangeLog>. Sincerely, The rsyslog Project Team _______________________________________________ rsyslog mailing list https://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
