2007-10-11 MonitorWare Agent 5.1 Final (Build Service 5.1.340/Client 5.1.1166)
MonitorWare Agent 5.1 Released Build-IDs: Service 5.1.340, Client 5.1.1166 New Additions EventLog Monitor Added new option to use the new Checksum method to verify if the LastRecord is still valid. This option can be set in each EventLogType. We also had to redesign the Client advanced options form, as all the options did not fit...
2007-08-22 MonitorWare Agent 5.0 Final (Build Service 5.0.336/Client 5.0.1161)
MonitorWare Agent 5.0 Released Build-IDs: Service 5.0.336, Client 5.0.1161 New Additions Forward Syslog Action– Added support for sending multiple messages over a persistent syslog/TCP connection. – Added capability to force -transport-tls like octet-counted framing for syslog/TCP connections. – Added a new major feature into this Action, Diskqueue. This new option is only available for TCP...
2007-07-03 MonitorWare Agent 4.4 Final (Build Service 4.4.332/Client 4.4.1137)
MonitorWare Agent 4.4 Released Build-IDs: Service 4.4.332, Client 4.4.1137 New Additions RFC 3195 Changes Enhanced Syslog/BEEP implementation for better interoperability with Cisco’s implementation in IOS. The BEEP support has been in our products for a long time, but so far no major vendor offered BEEP support. Now that a first major vendor implementation is available...
2007-01-22 MonitorWare Agent 4.3 Final (Build Service 4.3.323/Client 4.3.1099)
MonitorWare Agent 4.3 Released Build-IDs: Service 4.3.323, Client 4.3.1099 New Additions New EventLog Monitor V2 ServiceA new Service has been added to fully support the new EventLog of Windows Vista. Currently the Service is just called EventLog Monitor V2 and can only be configured and used on Windows Vista or Windows Longhorn Server. This new...
2006-10-25 MonitorWare Agent 4.2 Final (Build Service 4.2.316/Client 4.2.1062)
MonitorWare Agent 4.2 Released Build-IDs: Service 4.2.316, Client 4.2.1062 New Additions EventLog Monitor A ressource library cache has been added. This new feature will mainly be useful for the Eventlog Monitor. All libraries will be cached for 30 minutes by default. For events with the same reoccuring event sources, this will be a great performance...
