/monitoringlogfilesoptions.htm" />

Please enable JavaScript to view this site.

Navigation: Monitoring with EventSentry > Log File Monitoring

Consolidation & Monitoring Options

Scroll Prev Top Next More

Once a file has been added to a package, you will have to instruct EventSentry what to do with its content. You can either consolidate lines from the log file to a database, log the text to the application event log, or both. In addition, EventSentry allows you to include or exclude lines based on the keywords.

 

info_20

You can double-click the minus symbol - to remove all entries from the filter list.

 

Storing Log Files in a Database

To consolidate content from log files in a database, click the "Database Consolidation" tab and select a database destination from the "Destination" section by clicking the "Add" button. You can specify up to four different databases.

 

By default, all lines parsed from the log file will be sent to the specified database(s). To change this behavior, you can either exclude certain lines from being added to the database (include all, exclude some), or only send specific lines to the database. Click the + icon to add strings that will trigger the database.

 

Include: Log all lines to the database, except for exclusions below

This is the default setting, and it will send all parsed lines from the log file to the database. Lines in the log file containing strings that are listed below will not be sent to the database. This allows you to conserve space in the database if your log file contains unneeded content.

 

Exclude: Only log lines to the database that are included below

This setting is more restrictive and will only send lines from the log file to that database that are listed below. This allows you to only send content to the database that matches your filters. For example, you can only send lines that contain "Error" or "Warning" to the database to aid troubleshooting.

 

Load

Loads filter rules from a text file (one entry per line) and appends them to the current list of filters.

 

Logging lines from the log file to the event log

To log lines from log files to the application event log, click the "Event Log Alerts" tab and check the "Log to APPLICATION Event Log" check box. You can also select the severity under which entries in the event log are written as.

 

Context

When a matching line in a log file is found, the alert can contain up to 5 lines before and after of the matching line to provide context. Set to "None" to disable the log context feature.

 

By default, no lines parsed from the log file will be logged to the event log. Click the + icon to add strings that will trigger event log alerts.

 

Include: Log all lines to the event log, except for exclusions below

This setting will log all parsed lines from the log file to the event log. Lines in the log file containing strings that are listed below will not be logged to the event log. This setting is not recommended as it can quickly fill the application event log.

 

Exclude: Only log lines to the database that are included below

This is the default setting, and will log lines from the log file to the event log that match the strings listed below. This allows you to only send content to the event log that matches your filters. For example, you can only log lines that contain "Error" or "Warning" to the event log to aid troubleshooting.

 

Load

Loads filter rules from a text file (one entry per line) and appends them to the current list of filters.

 

Text Match Type

Specifies whether text matching uses simple wild card matching or regex pattern matching.