WinSyslog 5.3 Beta (Build 371)

– MonitorWare Echo Reply and Request Services, these two services together can be used to check in real-time if MonitorWare Agents are alive. The Echo Reply service is used on each of the installed agents. Then, a central agent is using the Echo Request and instructed to poll each of the other Agents. When the Request can not be carried out successfully, an alert can be generated. The MonitorWare echo protocol ensures that always a fresh probe of the remote agent is done.

– This new feature has been added. When enabled, the Agent will not stop processing the internal queue when it is stopped. Please note that it will remain in the stopping state then.

– Use CTRL + S to save your settings

– Move Rules & Actions up and down by using Toolbar buttons (Fast then the context menu)

– Highlighting of the current selected entry in the Tree view

– Reorder of the Rule & RuleSet menu.

– Is now saved. That means the Client will open exactly like you left it last time.

– Enhanced the filter editor with a few new features. This includes copy&paste, add comments per filter and minor others. The copy&paste feature works also between different rules and filter sets.

– Actions are also copy&paste able now. You can copy&paste them between rules and even rulesets if you want.

– Fixed a bug which could cause multiple socket errors if the mail server disconnected during transmission.

– When an empty Syslog tag value was configured in any service, garbage could be used instead. This has been corrected.

– Fixed a bug that could cause a leak of TCP Connections under stress circumstances (for example having more then 5000 failed connections per minute).

– In some cases the system does not free a socket fast enough (for example when you restart the service). An handler for this has been added which retries starting Services like syslog at least for one minute long.

– Removed a small and very unlikely memory leak that was caused by disabled actions.

– There was a bug in the “Send Syslog” action that could cause message text alteration if two or more “Send Syslog” actions were executed for the same message AND message text replacement was used in an action other than the last.

– There was a bug that could lead to registry file corruption if multi-line comments or messages were configured. Only customers working directly with registry files were affected.