Log Consolidator and Alerter
Log Consolidator and Alerter
MonitorWare Agent 8.0a Released Build-IDs: Service 8.0.412, Client 8.0.1343 Bugfixes Fixed a memory leak in all TCP releated actions that could occur if the TCP session timeout was set to a low value. Fixed a problem with the session timeout calculation for TCP releated actions. If the value was set above 3 minutes, the calculation […]
MonitorWare Agent 7.3a Released Release Date: 2011-05-16 Build-IDs: Service 7.3.402, Client 7.2.0.1326 Bugfixes Fixed a memory leak in all TCP releated actions that could occur if the TCP session timeout was set to a low value. Fixed a problem with the session timeout calculation for TCP releated actions. If the value was set above 3 […]
MonitorWare Agent 8.0 Released Build-IDs: Service 8.0.411, Client 8.0.1342 New Additions Added new Action called Send MSQueue: This action can send messages to the Microsoft Message Queuing Server. It is possible to customize the Queue Label, Priority and Queue Body. The Queue Body contains the message property by default as UNICODE (UTF16) string. In order […]
Adiscon is proud to announce the 8.0 release of MonitorWare Agent. This new major release focusses on international support. First of all, it now provides full IPv6 support throughout the complete engine, including all services and actions. This provides an easy transition to the new protocol just in time when the migration becomes more important […]
Adiscon is proud to announce the 7.3 release of MonitorWare Agent. This is a bugfixing release. This release only consists of bugfixes: Fixed a bug in conjunction with RawXML. Hardened SSL transmission send or receive handling. Corrected a SSL Error. Fixed a bug causing a crash on startup if a configured Syslog Port was blocked […]
MonitorWare Agent 7.3 Released Release Date: 2011-04-05 Build-IDs: Service 7.3.401, Client 7.2.0.1326 Bugfixes If RawXML Format was used as MessageFormat (EventLog Monitor V2), we now include the Eventlog Message in the <RenderingInfo> Node (if the message can be properly compiled). Hardened SSL transmission send or receive handling. This affects all Services/Actions which use SSL. Also […]
Step 4 – Setting up the Linux Clients We still need to implement the Linux clients into our logging network. This could be Linux workstations or servers. Currently, rsyslog is already shipped with many Linux Distributions as the default syslog daemon already. Though, often a rather old version is installed (mostly v3), this will be […]
Step 3 – Setting up the other Windows Servers We already have the central server and the regular Windows clients set up. We now need to set up the other Windows servers. We assume, that we have other Windows 2008 Servers. On these servers we want to monitor the local Event Log and textfile-based log […]
Step 2 – Setting up the Windows Clients Setting up the Windows Clients is rather easy. To do this, we only need to have EventReporter installed. EventReporter will be configured to pull the Windows Event Logs and forward them to our central syslog server via TCP syslog. Our example system will be Windows XP. When […]
Step 1 – Setting up the central log server: The central log server is the most important part of our central log storage and thus will be configured as the first part. And due to all the things it needs to do, it has the most work of course. When selecting your machine to install […]