EventLog Inspector Usage Examples

Instant Notification about Events that Have Occurred

Services and applications that do not have GUI should somehow inform the users about the results of the executed operations. For this reason, the operation system includes a number of system logs. An analysis of these logs is very useful to make a diagnosis of possible faults and to look for a way to fix them. Besides that, it is very useful to know about new events as soon as possible and not after some possible consequences have appeared. EventLog Inspector provides an opportunity to learn about system events almost at the same moment they arise. The user is instantly notified in popup windows.

Popup windows appear at the moment the event registers in the system log and stay on screen for some time or until the user closes them. Enough information is provided by them in a majority of cases to allow the user to analyze the situation, so there is no need to analyze logs with Windows Event Viewer.

One more important advantage of instant notification about system events is that the user can compare the actions he/she has performed and the system reaction to these actions. Thus, the reasons (if there are any) for the system event registration are obvious. There is no need to analyze a lot of events from the logs for the last several hours and remember what exactly was going on during some period of time.

Forwarding Windows Events to Syslog Server

Syslog protocol is supported by almost all network devices and many operating systems. That is why it is a convenient way to organize a common center for collecting information on the network situation. Unfortunately, Microsoft Windows does not include a built-in feature for transferring its system events to syslog standard. EventLog Inspector compensates for this drawback and translates events to a syslog server.

Thanks to a flexible syslog format that supports EventLog Inspector, it is possible to generate syslogs that are compatible with a certain installed syslog server. This way, a maximum amount of information will be transferred.

Collecting system information in one place significantly simplifies network centralized administrating. When the filtration and notification are configured correctly, the administrator will learn about the problems arising on remote computers on time.

Two Ways of E-mailing Windows Events

EventLog Inspector makes it possible to forward system messages to an e-mail box and makes up for the operating system drawback. This functionality can be useful in two cases. The first example of this feature's application is notifying the user about important system events by e-mail. Having set an immediate sending and special filtering, the system administrator will be notified about important events registered on network computers.

The second way of using it is sending a complete list of events for some period of time, the so-called consolidated report. Troubleshooting is simplified in this case because there are reports containing all necessary registered events from all network workstations in the administrator's mailbox.