Step-by-Step Guide: Building a Custom Windows Event Logger Notifier

Quick Links

• How It Works
• Configuration
• Examples

The Windows Event Logs are a tremendous resource as they can not only help you troubleshoot current system issues, but can also provide you with warning signs of potential future problems. So keeping on top of the events your system records can be key to keeping your system running as it should. Unfortunately, sifting through the Event Logs or creating custom views can be a cumbersome manual process.

Thankfully, we have a solution which will easily allow you to export and filter Windows Event Log entries and then have them emailed and/or saved to a text file. When this process is configured as part of a scheduled task you can have, for example, warning and error messages emailed to you automatically.

How It Works

Our solution works by using a freeware utility, MyEventViewer, by Nirsoft which allows you to easily export Windows Event Logs to a comma separated file. Based on this output, we have developed an easy to configure batch script which filters these results and then can email and/or save the filtered results file. Because the results are a comma separated file, it can be opened in Excel (or your favorite CSV program) and further sorted and filtered.

Configuration

The configuration settings and options are documented as inline comments in the script, however we will cover a few of them in a bit of detail here.

Event Log Name

When specifying the Event Logs you want to capture the events from, you must use the system full name of the log. This is not necessarily what you see in the Event Viewer list of logs.

For example, if you wanted to capture events from the “Microsoft Office Alerts” log, go to the Properties dialog of the log.

Click here

Note the value in the Full Name value, in this case “OAlerts”. This would be the value you would need to enter into the script’s configuration.

Event Types

The values for the Event Types is simply the text you see in the “Level” column when you are viewing Event Logs. Typically these are either Information, Warning or Error but various logs may have different values.

Scheduled Task Setup

The typical usage of this script is most likely in an automated process. So to make sure there is no overlap between your capture interval and when the process runs, you should set up a Windows Scheduled Task to complement the capture time.

Quite simply, if your configuration is set to capture events for the last day, you should have a scheduled task that runs once per day. If your configuration is set to capture for the last hour, your scheduled task should be set to run once every hour. Etc.

As an additional note, in order to make sure the MyEventViewer application can get to the information it needs, the respective scheduled task should be run with administrator rights on the machine.

Examples

This configuration would email Errors and Warnings from the System and Application Event Logs recorded in the past day (24 hours) to my@email.com as well as save the output to the C:\EventNotices folder:

• EmailResults=1
• EmailTo=my@email.com
• SaveResults=1
• SaveTo=C:\EventNotices
• TimeInterval=3
• TimeValue=1
• Logs=System,Application
• Types=Error,Warning
• Scheduled Task should run every day.

This configuration would only email Errors from the System Event Log recorded in the past hour to my@email.com :

• EmailResults=1
• EmailTo=my@email.com
• SaveResults=0
• TimeInterval=2
• TimeValue=1
• Logs=System
• Types=Error
• Scheduled Task should run every hour.

This configuration would only save Errors and Warnings from the Application Event Log in the past week to the desktop of user JFaulkner (Windows 7) C:\Users\jfaulkner\Desktop:

• EmailResults=0
• SaveResults=1
• SaveTo=C:\Users\jfaulkner\Desktop
• TimeInterval=3
• TimeValue=7
• Logs=Application
• Types=Error,Warning
• Scheduled Task should run every week.

Download Event Log Notifier Script from How-To Geek

Download MyEventViewer from Nirsoft

Download Blat from Sourceforge

Also read: