Monitoring Non-Events
Learn how to monitor 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 Non-Events user guide.
Example list of monitored 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 messages are not in time (or exist at all within defined thresholds)
- Evaluate a number of events - Make sure you are alerted and aware when there are too many or too few.
State evaluation for Non-Events
One (1) configuration will be displayed within Nodinite as one Resource. If you have 42 Non-Events configurations, then you will have 42 Resources in Nodinite.
- The name of the Resources comes from the name of the configuration
- All configurations belong to the 'ACK/NAK' Category
- The Application name is the same as the Resource name
Each 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' is not possible either due to network or security-related problems | Review prerequisites | |
| Error | Error threshold is breached | Too few or too many events are detected | Edit thresholds for 'Full Interval' Details for 'Full Interval' Edit thresholds for 'Monthly Interval' Details for 'Monthly Interval' Edit thresholds for 'Partial Interval' Details for 'Partial Interval' Edit thresholds for 'Partial Interval - Sliding Window' Details for 'Partial Interval - Sliding Window' Edit thresholds for 'Partial Interval - Sliding Window Multiple Days' Details for 'Partial Interval - Sliding Window Multiple Days' | |
| Warning | Warning threshold is breached | Too few or too many events are detected | Same Actions as above | |
| OK | Within user-defined thresholds |
|
Not logically applicable |
From within Nodinite, you can reconfigure the state evaluation on the Resource level using the Expected State feature.
Here's an example of an evaluation with the current date is in the list of dates to ignore.
Edit thresholds
Managing thresholds for ACK/NAK is detailed in the Configuration user guide.
Alert history for Non-Events
During root cause analysis or other purposes, it might be helpful to understand how often your 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 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 configuration |
Frequently asked questions
Use the troubleshooting guide to find the FAQ and answers to known problems.
How do I enable monitoring of Non-Events
To Monitor 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 a disabled monitoring configuration.