Automate monitoring of content-based files

This guide shows you how to automate monitoring of content-based files using the Nodinite Log File Parser Monitoring Agent. You will learn how to configure monitoring, set up RegEx filters, and leverage Nodinite's alerting and diagnostics to proactively detect and resolve issues across multiple files and formats.

On this page, you will learn how to:

✅Automate inspection of content in text-based log files—even across multiple files
✅Use RegEx filters to target specific patterns and business-critical events
✅Get real-time alerts for matching content and errors
✅Integrate with Monitor Views and manage resources efficiently

Diagram: Visual overview of how Nodinite inspects content in multiple file shares and triggers alerts based on matching content.

To get you started, let's look at a quick example to help you understand a use case. Below is a sample XML file where the system has rejected the Order Response.
A rejected Order Response is probably inadequate for your business, and you should get an alert that this situation exists. In your real-world scenario, you might have other entities that you would like to monitor, and since the Nodinite Log File Parser Monitoring Agent uses RegEx expressions, most use cases should be possible to cover.

<ns0:OrderResponse xmlns:ns0="Common.Schemas/Nodinite/1.0">  
    <Order>  
        <Id>101</Id>  
        <Status>OK</Status>          
    </Order>  
    <Order>  
        <Id>102</Id>  
        <Status statusCode="1337">REJECTED</Status>                  
    </Order>  
</ns0:OrderResponse>  

Before you begin

Ensure you comply with the prerequisites and install the Nodinite Log File Parser Monitoring Agent.

Step 1: Add a new monitoring configuration

To add a new monitoring entry, click the Add button from the Log File Events tab.

Content tab in Nodinite Log File Parser Monitoring Agent.

1. Name the configuration
2. Provide an optional description
3. Set the Application ID (You must have a matching entry in the Applications Tab)

General tab for configuration details.

Step 2: Set the monitor path

Next, enter the path to where the log files with events to correlate are located (for example, C:\Temp\BizTalk\INT001 Orders\Out).

1. Enter the path
2. Enter the RegEx-based filter (\.xml$)

Path tab for specifying log file location and filter.

Below is a table with some common RegEx file filter examples:

Step 3: Set the start match

Next, enter the start match configuration.

1. The files with arbitrary content do not need a date-time; hence, you can safely uncheck the 'Lines have a DateTime' checkbox
2. In this case, we are looking for a line that contains a statusCode - statusCode="[0-9]+"

Start match tab for RegEx pattern configuration.

Step 4: Set the time-related options

1. Leave the Clear Date Time field empty for now. This field is populated by the system when an end-user is clearing previous problems.
2. Select the time option (Modified after clear date-time)
3. Uncheck the 'Lines have a DateTime' checkbox

Save

You must click 'Save' or 'Save and close' for changes to persist. The new settings/thresholds are evaluated on the next synchronization.

Here's an example of the Save options.

Note

The delay in presenting the new evaluated state depends on the monitoring agent's synchronization interval

Save and close, save, and close the dialogue.
Cancel, closes the dialogue without saving any changes.

Step 5: Configure the Monitor View

Next, add the named Resource to a Monitor View.

• Follow the 'Add or manage Monitor View' user guide.

Here's an example of a Monitor View with errors detected in correlated log files

You can further review the details about the errors by clicking on the Actions button and then clicking on the Error Report menu item.

Error Report action in Monitor View.

This action opens a new modal with a list of all log files with an active error (> last clear date-time).

Do note that the monitoring may span multiple files(!)

Additional information is available if you expand the row.

Expanded error details in the Error Report.

Tip

You can ignore old errors by clicking on the Clear Errors menu item in the Actions button. The Resource is then OK until a new entry matches the configuration.

Next Step

• How to monitor correlated events
• How to monitor the IIS (W3SVC) log files

Related Topics

Nodinite File Monitoring Agent