We have just released EventReporter 19.4, bringing native YAML ecosystem integration, improved administrative resilience, and critical service engine stability to our Windows Event Log forwarding solution. This release focuses on configuration flexibility, reliable service state management, and continuous local logging availability under high-volume production workloads.
A key highlight of this version is the addition of native YAML configuration file import and export, which is now fully aligned with the service runtime loader. By bringing file-based configuration tools directly to the Configuration Client, EventReporter 19.4 provides a seamless path for administrators to audit, modify, and migrate system settings without needing to work directly with registry objects.
To reduce administrative friction during configuration updates, the product features improved version-compatibility handling. The Configuration Client will now skip unrecognized blocks from newer service versions with a clear warning instead of completely failing to initialize, preventing version mismatches from interrupting administrative tasks.
Furthermore, this update introduces enhanced service control and state monitoring mechanisms, improving process stability across transitional states and adding safeguards to help administrators handle orphan processes or localized access right limitations.
Technical improvements in EventReporter 19.4
This release includes significant hardening of the file engine, mail handling subsystems, and background client threading:
- Resilient File Logging and Rotation: Fixed an asynchronous log rotation issue after configuration reloads, allowing rotated files to finalize properly without requiring service restarts. Scheduled checks are now bypassed when a log file is missing, eliminating repeated rotation attempts for absent files, while overall rotation reliability has been strengthened during rapid reloads, shutdowns, cache cleanup, and high-volume dynamic file routing.
- Persistent Event Checkpointing: The Event Monitor service now automatically saves event checkpoints if a system shutdown interrupts a configured delay, significantly reducing duplicate event processing when the system boots back up.
- Reliable Service Control Operations: Streamlined service control behaviors resolve false stop-timeout errors when a service has already successfully reached its target state in Windows Services. The client now supports optional process termination and includes a native shortcut directly to the Windows Services management console.
- Operational Visibility: Refined status bar tracking brings immediate clarity during rapid infrastructure adjustments, precisely showing transitional phases such as Stopping, Starting, and Paused (Reloading). Additionally, the Service Management event viewer now automatically prepends new events after actions like start, stop, or reload rather than completely clearing the history list.
- Resource and Output Cleanup: Improved background timers ensure clean structural shutdowns within the Mail Action module. Spurious error-level reports generated during idle connection recycling inside the Send SETP action have also been successfully reduced.
- Engine and Client Hardening: Addressed a potential shutdown crash affecting instances where the Event Viewer or Service Management panel remained open at client exit. Background threading logic has also been improved to safely recover from aborted operational loops.
EventReporter 19.4 remains the premier choice for organizations that need to reliably bridge the gap between Windows Event Logs and central Syslog or database repositories.
Released versions
- Service: 19.4.0.496
- Client: 19.4.0.585