Parsing log messages
This article describes how to parse log message via “Post-Process”. It illustrates the logic behind Post-Process action. Get relevant information from logs Log files contain a lot of information. In […]
This article describes how to handle syslog messages from Unix/Linux systems that do not follow RFC 3164 standard formatting. The Problem Some Unix/Linux systems (historically Solaris 8/9, but also found […]
Last updated 2016-09-28 by Pascal Withopf, using Winsyslog 13.3. In this scenario, an event log monitor is used to forward all events written to the NT Event Log to a […]
Last updated 2016-08-26 by Jan Gerhards, using Winsyslog 13.2. In this scenario, a simple Syslog server will be created. No other services are configured. The Syslog server will operate as a […]
1. Start the Application. 2. Select your language – in this example, I use English, so it might be a good idea to choose English even if that is not […]
Information for a Mass Rollout A mass rollout in this context means deploying an Adiscon client (for example MonitorWare Agent, EventReporter, or WinSyslog) to more than a handful of systems […]
WinSyslog and EventReporter are subset of MonitorWare Agent. This means that there would be no difference in the set up creation.You need administrative privileges on each of the machines. This […]
1. Start the Application. 2. Again, you can select the language to use. And again, I suggest using English, as this makes the guide easier to follow. 3. Then define […]
1. You would at least need the Basic Edition of MonitorWare Agent / WinSyslog / EventReporter for this scenario. Please Note: We are using MonitorWare Agent in this guide whereas […]