- 4 minutes to read

How to monitor Nodinite Log Audits

Detect integration errors before they impact your business by proactively monitoring the Nodinite Log Audit trail. This guide shows you how to configure the Nodinite Web Service Monitoring Agent to check for error-level log audit entries and receive timely alerts.

✅ Instantly detect integration errors recorded in Nodinite Log Audits
✅ Automate error monitoring with configurable polling intervals
✅ Receive actionable alerts when error-level log audit entries are found

This guide provides instructions for configuring the Nodinite Web Service Monitoring Agent to monitor the Nodinite Log Audits Web API for error-level entries.

graph TD A[Web Service Configuration] --> | Evaluate Log Audits | B{Items Empty?} B --> | Yes | E[OK] B --> | No | F[Error]
*Diagram: The Web Service Monitoring Agent evaluates the Log Audits API. If no error-level items are found, the state is OK; if errors exist, an Error state is triggered.*

The Nodinite Web Service Monitoring Agent enables you to monitor if error-level log audit entries exist by evaluating the body of the HTTP/HTTPS response from a call to the Nodinite Web API.

The Web Service configuration you create will become a Resource in one or more Monitor Views where you can track the evaluated state in real time.

Step 1: Add a new Application

Logically identify and group monitored Resources using the Applications feature. Manage these in the Applications tab for your selected instance of the Nodinite Web Service Monitoring Agent.

  • Click the Add button
  • Enter Name and a unique id. For example, use Nodinite as Name and 1337 as the unique Id. You can use any unique values.

Step 2: Add a new Web Service Monitoring Configuration

Configure what to monitor—in this case, the Nodinite Log Audits Web API.

  • Click the Add button
  • Expand the empty entry by clicking on the accordion

Step 3: Basic tab

Name your configuration by editing the following fields in the Basic tab:

  • Make sure the configuration is enabled (checked)
  • Set the Display name to a logical name, e.g., Monitor Nodinite Log Audits for Errors
  • Set the Description to provide context, e.g., Alert when error-level log audit entries exist in Nodinite
  • Select the Application you created in Step 1

Step 4: Advanced tab

Manage your time-related thresholds in the Advanced tab:

  • Set the Polling Interval (e.g., 300 seconds for frequent checks)
  • Set the Request Timeout (e.g., 30 seconds)
  • Check Allow Retries
  • Set the Number of retries (e.g., 3) to avoid false alerts
  • Set the Retry Status Code to OK to ignore errors during retries

Step 5: Request tab

Configure the actual Request in the Request tab:

http://localhost/Nodinite/Dev/WebAPI/api/logaudits?numberOfItems=25&page=1&level=3&fromDate=2024-01-01&orderBy=SequenceNumber%20DESC

Replace Dev with your environment name (e.g., Test, Prod). Use localhost if the Web Service agent is installed on the same server as the Web API.

Parameter Value Description
numberOfItems 25 Maximum number of items to return per page
page 1 Page number for paginated results
level 3 Log level filter: 3 = Error
fromDate 2024-01-01 Start date for the log audit search
orderBy SequenceNumber DESC Sort order for the results
  • Set the method to Get

Leave the rest of the fields empty. The Web API does not require additional HTTP headers for this request.

Step 6: Response tab

Configure response validation in the Response tab:

  • Set the Status Code to 200 (OK)
  • For this type of check, you can usually leave performance checkboxes unchecked

Step 7: Evaluate response body tab

Configure evaluation of the HTTP response body in the Evaluate response body tab. The Nodinite Log Audits API returns a JSON object where the Items property is an array of log audit entries. When Items is empty, no error-level entries exist.

  • Select Expression Type: Regex Match
  • Enter the following Expression:
"Items"\s*:\s*\[]
  • Set the Expected Result to:
"Items":[]

This expression matches when the Items array in the response is empty, meaning no error-level log audit entries exist. If error entries are found, the match fails and the monitoring state changes to Error.

Leave the rest of the fields at their default values.

Step 8: Authentication tab

If the Web API application pool account is not the same as the Windows Service account running the Nodinite Web Service Monitoring Agent, provide alternate credentials in the Authentication tab:

  • Check Use Windows Authentication
  • Enter the Domain User: DOMAIN\user (the user must have access to the Nodinite Web Client)
  • Enter the Password for the user

Step 9: Save configuration

Click Save to persist your configuration.

Step 10: Create a Monitor View and configure alerts

Configure a Monitor View and select an Alarm Plugin to receive alerts in your preferred way. These steps are detailed in the Add or manage Monitor View user guide.

Make sure to select the Resource you named in Step 3.

Next Step

Add or manage Monitor View
Add or manage a Monitoring Agent Configuration

Monitoring Agents
Monitor Views
Administration
Log Audits