Monitoring ACK/NAK Non-Events
Learn how to monitor ACK/NAK Non-Events (one or more correlated Responses are timely delivered after the initial Request)
This section describes what's being monitored and the rules for how Nodinite translates this into meaningful monitoring states. Also, some remote commands are available as Actions to help you swiftly manage problems. Available Remote Actions are further detailed in the Managing ACK/NAK Non-Events user guide.
Example list of monitored ACK/NAK Non-Event configurations in a Nodinite Monitor View.
Monitoring Features
- State Evaluation - Make sure you get alerted when thresholds are breached!
- Duration check - Makes sure you are alerted and aware when responses are not in time (or exist at all within defined thresholds)
- Evaluate number of events in correlation - Makes sure you are alerted and aware when there are too many responses (usually duplicates)
State evaluation for ACK/NAK Non-Events
One (1) ACK/NAK configuration will be displayed within Nodinite as one Resource. If you have 42 ACK/NAK Non-Events configurations, then you will have 42 Resources in Nodinite.
- The name of the Resources comes from the name of the ACK/NAK configuration
- All ACK/NAK configurations belong to the 'ACK/NAK' Category
- The Application name is the same as the Resource name
Each ACK/NAK configuration (presented in Nodinite as a Resource) has one of the following evaluated states at any given moment:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'Non-Events ACK/NAK' is not possible either due to network or security-related problems | Review prerequisites | |
| Error | Error threshold is breached |
|
Show missing events Clear previous errors | |
| Warning | Warning threshold is breached |
|
Show delayed events Clear previous errors | |
| OK | Within user-defined thresholds | No late or missing responses currently exists | Not logically applicable |
From within Nodinite, you can reconfigure the state evaluation on the Resource level using the Expected State feature.
Remote Actions
Edit thresholds
Managing thresholds for ACK/NAK is detailed in the Configuration user guide.
Alert history for ACK/NAK Non-Events
During root cause analysis or other purposes, it might be helpful to understand how often your ACK/NAK Non-Events problems happen. If your Monitor View allows it, you can search for historical state changes for the provided time span, either for all your ACK/NAK Non-Events or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.
| Search | Resource history |
|---|---|
 Search for alert history for all resources in the Monitor View |
 Alert history for the selected ACK/NAK configuration |
Frequently asked questions
Use the troubleshooting guide to find the FAQ and answers to known problems.
How do I enable monitoring of ACK/NAK Non-Events
To Monitor ACK/NAK Non-Events, the Agent must be configured with the Enable monitoring checkbox checked (default is checked) further detailed in the 'Configuration' user guide.
The screenshot below is from the remote configuration form available from the Monitoring Agents administration page.
Example with disabled ACK/NAK monitoring configuration.