Monitoring Custom Event Logs

Navigation: Monitoring with EventSentry > Event Log Monitoring >

With Custom Event Logs you can categorize event records by their event source and store them in a separate event log. This can be useful if you would like to organize events by their source. In so doing, you are redirecting the log entries to an event log that you specify.

On Vista and later, the custom event log tab can also be used to monitor "Applications and Services Logs", for example the "Microsoft-Windows-TaskScheduler/Operational" event log.

For example, you can create a custom event log called Web Server, which stores events from the sources IISADMIN, SMTPSVC and VBRuntime.

Events from these specified sources are written to a different event file (and not written to the default event log file). Custom event log files are stored in the %SYSTEMROOT%\SYSTEM32\CONFIG directory by default; the same location where the default log files (Application, Security, System etc.) are stored.

EventSentry makes it easy for you to manage custom event logs without requiring you to manipulate the registry manually. EventSentry takes care of creating all registry keys and registry values. It even takes care of moving message file information into the custom event log so that viewing event details works as expected.

You can also monitor these custom event logs with EventSentry, which will support a maximum of 30 custom event logs (in addition to the 3-6 default event logs).

EventSentry does not support monitoring the "Forwarded Events" or "EventCollector" event logs. All other event logs can be monitored in real time.