ACK/NAK Configuration
Unlock the power of correlation-based monitoring from the Logging with Nodinite! This guide shows you how to configure ACK/NAK monitoring using grouped Log Views, set up advanced thresholds, and detect anomalies for seamless integration and business assurance.
✅ Proactively detect missing or delayed business-critical messages
✅ Set up real-time alerts for correlation-based scenarios
✅ Leverage grouped Log Views for advanced monitoring and anomaly detection
✅ Empower your business with flexible, step-by-step configuration
This guide walks you through how to configure the Nodinite Non-Events Monitoring Agent to deliver real-time alerts from ACK/NAK Monitoring configurations, using results from Nodinite Log Views.
Nodinite offers two powerful configuration types for Non-Events Monitoring:
- ACK/NAK (this page) – Monitor based on correlation using a grouped Nodinite Log View.
- Non-Events – Monitor based on the number of rows from a search operation on a Nodinite Log View.
Leverage grouped Log Views to ensure you receive the next expected message within the right time window. This feature also enables sanity checks so you can detect duplicates and other anomalies in your message flows.
This capability proves invaluable for order/order-response, invoice/payment, and action/reaction scenarios—ensuring you account for every business-critical message.
ACK/NAK
The ACK/NAK tab lets you manage one or more correlation-based configurations for precise, real-time monitoring.
Example of the ACK/NAK configuration tab.
- Click the
Addbutton to create a new ACK/NAK configuration.
Add a new ACK/NAK Monitoring configuration. - Expand the accordion to reveal configuration details.
- Repeat as needed for multiple configurations.
Basic Tab
In the Basic tab, provide essential details for your ACK/NAK configuration.
Example of an ACK/NAK configuration—one accordion per entry.
- Enabled – Activate or deactivate this ACK/NAK configuration.
- Name – Enter a user-friendly display name.
- Description – Add a clear description for this configuration.
- Log View API URI – Specify which 'Log View' to use. Copy and paste the URI from the 'Copy API URI' dialog in the Log View.
Copy the address from a Log View after you perform a search.
Copy the API URL from a Nodinite Log View for use in your ACK/NAK configuration.
Info
The system generates the URL, but you may need to adjust it for your IIS environment. If the agent runs on the same server as Nodinite Core Services, try
http://localhost/...instead.
- Search time span – Define how far back to search for events (days.hours:minutes:seconds, e.g., 7.12:30:59).
Note
If the grouped Log View has a Time Interval Configuration, make sure it allows detailed time searches and does not use pre-defined intervals.
Override start date time (UTC) – Set a specific start date/time for event searches, overriding the default if newer than the search time span.
A User in the Nodinite Web Client can update this field by issuing a 'Clear the alert' Remote Action from a Monitor View with the Resource.
Advanced Tab
Fine-tune your monitoring with advanced options:
- Maximum number of groups to evaluate – Limit the number of groups for evaluation. Higher values may impact performance.
- Warn when delayed records are found – Enable to receive warnings for delayed events within the defined search time span.
Limit the number of groups to evaluate and other advanced options.
Evaluation Tab
Set up the logic for message correlation and alerting:
- Warning time span – Set the maximum allowed time to wait for the next event before raising a warning (days.hours:minutes:seconds).
- Error time span – Set the maximum allowed time to wait for the next event before raising an error.
- Evaluate the number of events in the group – Enable to apply user-defined thresholds to group counts.
- Use 'EndpointId' matching – Use this if ACK and NAK events share a message type but occur on different ports.
Ignore Dates Tab
Add one or more repeating dates to ignore in monitoring.
Example of the Ignore Dates tab for ACK/NAKs.
- Click the
Addbutton to add dates to ignore.
Add ignore dates for ACK/NAK monitoring. - Expand the accordion for details.
- Repeat as needed.
| Example | Description |
|---|---|
| YYYY | Replace the current year |
| MM | Replace the current month |
| DD | Replace the current day |
Note
The starting date of a grouped Log Event is ignored.
Scheduling Tab
Learn more about scheduling in this guide (shared for Non-Events and ACK/NAKs).
Authentication
Apply impersonation if the service account running the Non-Events Monitoring Agent lacks access to the Log View.
We recommend you create a dedicated Non-Events role for the service account and add it to all Log Views to be monitored. This step often eliminates the need for impersonation.
- Use Impersonation – Check to impersonate the call to the Log View. By default, the agent's account is used.
If you check this, (*) appears in the Authentication tab, indicating impersonation is active.
Enter credentials for the account with Log View access rights.
Next Step
Scheduling – Set a period to limit call frequency. This step is crucial to prevent system overload and keep Nodinite responsive.
Add or manage a Monitoring Agent Configuration
Add or manage Monitor View
Related Topics
Configuration
Install Nodinite Non-Events Monitoring Agent
Monitoring Agents
Applications