WinSyslog

WinSyslog 17.4 Released

Adiscon is proud to announce the 17.4 release of WinSyslog. This advanced update focuses on providing reinforced stability and enhanced error-handling capabilities to our valued users. One of the prominent updates includes fortifying the Syslog Action, which had a very rare chance of attempting to initiate multiple TCP connections to the same target simultaneously. Our […]

WinSyslog 17.3 Released

Adiscon is proud to announce the 17.3 release of WinSyslog. This is a maintenance release with minor bugfixes. Most important, the libraries OpenSSL and librelp have been updated to the latest available versions to maintain the highest level of security. The engine stability has been further improved by fixing minor issues. Detailed information can be […]

Review log database with InterActive SyslogViewer

With every purchase of WinSyslog or MonitorWare Agent, we also provide a complimentary license key for InterActive SyslogViewer. This is a small tool that allows for two things: 1. Live view of syslog logstream 2. Review of log database In this guide, we will concentrate on the setup process for reviewing logs that are stored […]

WinSyslog 17.2 Released

Adiscon is proud to announce the 17.2 release of WinSyslog. Most important, the Syslog TCP Receiver can define a maximum message size limit and we can optionally detect the year after the RFC3164 timestamp. Syslog TLS support was added to the Syslog Test Message Tool (Configuration Client). The engine stability has also been further improved […]

WinSyslog 17.1 Released

Adiscon is proud to announce the 17.1 release of WinSyslog. We have hardened the Service code further and fixed multiple minor bugs. Detailed information can be found in the version history. Version 17.1 is a free download. Customers with existing 16.x keys can contact our Sales department for upgrade prices. If you have a valid […]

WinSyslog 16.2a Released

We are proud to announce the 16.2a release of WinSyslog. This is a minor update for the last maintenance release of this major Version. A problem was solved that happened when the user stopped the service while a configuration reload was active. Detailed information can be found in the version history. Detailed information can be […]

Scroll to top