The following issues were resolved in the Event Streamer module 2.0.38 release.
Tracking number | Summary |
|---|---|
ENDPT-111724 | The issue with data not being delivered from Event Streamer module to Syslog server unless the policy settings are saved in the module UI, has been resolved. |
ENDPT-112522 | The issue concerning the Event Streamer module, where logs were not forwarded to Helix after upgrading from version 1.x to 2.x unless the 'Stream to Company Helix' toggle option under Helix configuration settings was enabled, has been resolved. |
ENDPT-112551 | The issue with Event Streamer module consuming all available CPU resources, resulting in a spike in CPU utilization up to its maximum capacity, and consequently failing to log any events or send them to Helix, has been resolved. |
ENDPT-112596 | The issue regarding the Event Streamer module's default configuration for the 'TerminalServices' event type, which was set to log only local events, has been resolved. |
ENDPT-112607 | The issue concerning the Event Streamer module failing to transmit DNS logs to Helix, has been resolved. |
ENDPT-112675 | The issue with Event Streamer module adding custom-added event IDs that were not visible in both Helix and Helix policies when the Event Streamer module is upgraded from version 1.x to 2.x, has been resolved. |
ENDPT-112775 | The issue with custom settings in the Event Streamer module UI configuration resetting to their default value and failing to retain the modified value when Event Streamer module is upgraded from version 1.x to 2.x, has been resolved. |