Monitoring Non-Events
Proactively monitor Non-Events with Nodinite and make sure your business never misses a critical response. This guide shows you how to configure, monitor, and act on Non-Events, so you resolve issues before they impact your operations.
- ✅ Instantly receive alerts when event volumes are too low or too high
- ✅ Monitor every Non-Event configuration as a unique resource
- ✅ Take immediate action with remote actions and clear state evaluation
- ✅ Analyze alert history for rapid troubleshooting and continuous improvement
Nodinite gives you the power to monitor, alert, and act on Non-Events with unmatched precision. This guide explains what you monitor, how Nodinite translates technical events into actionable monitoring states, and how you use remote actions to resolve issues instantly. For a deeper dive into available Remote Actions, see the Managing Non-Events user guide.
You can easily view and manage all monitored Non-Event configurations in a Nodinite Monitor View.
Monitoring Features
- State Evaluation – Instantly receive alerts when thresholds are breached, so you never miss a critical event!
- Duration Check – Get alerts when responses are late or missing, so you stay ahead of potential issues.
- Correlation Count – Receive notifications if you detect too many or too few responses, helping you quickly spot anomalies.
State Evaluation for Non-Events
Nodinite displays each Non-Events configuration as a unique Resource. For example, if you create 42 configurations, you monitor 42 distinct resources, each independently.
- The Resource name matches the configuration name.
- Each configuration appears under a Category based on its interval type:
- Full Interval → Category: "Full Interval"
- Partial Interval → Category: "Partial Interval"
- Partial Interval - Multiple Days → Category: "Partial Interval - Multiple Days"
- Partial Interval - Sliding Window → Category: "Partial Interval - Sliding Window"
- Partial Interval - Sliding Window - Multiple Days → Category: "Partial Interval - Sliding Window - Multiple Days"
- Monthly Interval → Category: "Monthly Interval"
- The Application name mirrors the Resource name.
Nodinite continuously evaluates every Non-Events configuration (as a Resource) and assigns one of the following states:
With Nodinite, you can easily reconfigure state evaluation at the Resource level using the Expected State feature, so you tailor monitoring to your business needs.
This example shows an evaluation where the current date is in the list of dates to ignore.
Edit Thresholds
Fine-tune your monitoring thresholds for Non-Events in the Configuration user guide.
Understanding Non-Events Interval Types
Nodinite provides flexible interval types to match your business monitoring requirements. Each interval type serves specific use cases and evaluates events differently. Understanding these interval types helps you configure precise, actionable alerts.
Full Interval Monitoring
The Full Interval monitors the entire search time-span you configure. This interval type evaluates all events within the specified duration and triggers alerts when the total count falls outside your defined thresholds.
When to use Full Interval:
- Monitor daily, weekly, or custom period totals
- Track overall system health across extended periods
- Ensure minimum/maximum transaction volumes over long durations
How it works: Nodinite queries your Log View for all events within the search time-span (e.g., last 24 hours, last 7 days). The system counts the total events and compares this count against your Warning and Error thresholds.
Example scenario:
You expect between 1,000 and 1,500 invoices per day. Configure Full Interval with:
- Search time-span:
1.00:00:00(1 day) - Warning thresholds: Min 950, Max 1,550
- Error thresholds: Min 900, Max 1,600
If your system processes only 850 invoices in 24 hours, Nodinite triggers an Error alert.
Configuration: See Full Interval Configuration for setup instructions.
Partial Interval Monitoring (Default)
The Partial Interval (Default) type monitors specific time windows within your search time-span. This allows you to monitor different periods with different thresholds, providing granular control over your alerting strategy.
When to use Partial Interval (Default):
- Monitor business hours separately from after-hours
- Track different transaction volumes for morning vs. afternoon
- Apply different thresholds to specific time windows
How it works: You define a start and end time (day + time) for the interval. Nodinite evaluates this interval only after the current time passes the end time. The system filters events within your search time-span to include only those falling within the partial interval window.
Example scenario:
You process customer orders mainly between 8 AM and 6 PM on weekdays. Configure a Partial Interval:
- Start: Monday 08:00:00
- End: Monday 18:00:00
- Search time-span:
7.00:00:00(7 days) - Error thresholds: Min 200, Max 500
Nodinite evaluates this interval every Monday after 6 PM, counting events that occurred between 8 AM and 6 PM that day.
Configuration: See Partial Interval Configuration for setup instructions.
Partial Interval - Multiple Days
The Partial Interval - Multiple Days type repeats the same Partial Interval configuration across multiple selected days of the week. This eliminates the need to create separate configurations for each day.
When to use Multiple Days:
- Apply the same monitoring rules to weekdays (Monday-Friday)
- Monitor weekend processing with different thresholds than weekdays
- Track recurring daily patterns across selected days
How it works: You configure one interval with start/end times and select which days of the week to apply this configuration. Nodinite creates independent evaluations for each selected day.
Example scenario:
Your warehouse processes shipments Monday through Friday, 9 AM to 5 PM, with consistent volume expectations:
- Days: Monday, Tuesday, Wednesday, Thursday, Friday
- Start time: 09:00:00
- End time: 17:00:00
- Error thresholds: Min 50, Max 150
Nodinite evaluates each weekday independently after 5 PM, ensuring shipment volumes stay within expected ranges.
Configuration: See Partial Interval Configuration for setup instructions.
Partial Interval - Sliding Window
The Partial Interval - Sliding Window type provides continuous, rolling evaluation of your events. Unlike the Default type, which evaluates only after the end time, Sliding Window evaluates constantly once the window becomes active.
When to use Sliding Window:
- Monitor real-time SLA compliance
- Track response times within moving time windows
- Detect issues immediately when they occur, not after a fixed period ends
How it works: You define a start time and duration (floating span). Once the current time passes the start time plus the floating span, Nodinite begins continuous evaluation. The system evaluates a moving window that always looks back the specified duration from the current moment.
Example scenario:
You monitor API response acknowledgments with a 2-hour SLA. Configure Sliding Window:
- Start time: 00:00:00 (midnight)
- Floating span: 2 hours
- Window becomes active: 02:00:00
- Error threshold: Min 1 (at least one acknowledgment required)
At 10:30 AM, Nodinite evaluates events from 08:30 AM to 10:30 AM. At 2:45 PM, it evaluates events from 12:45 PM to 2:45 PM. This provides continuous monitoring.
Visual explanation of Sliding Window:
Diagram: Sliding Window moves continuously throughout the day, evaluating a 4-hour window at each check. Green indicates active evaluation periods.
Configuration: See Partial Interval Configuration for setup instructions.
Partial Interval - Sliding Window Multiple Days
The Partial Interval - Sliding Window Multiple Days type combines the continuous evaluation of Sliding Window with the day-selection capability of Multiple Days. This provides the most flexible monitoring option.
When to use Sliding Window Multiple Days:
- Apply continuous monitoring across selected weekdays
- Monitor business-hours SLAs Monday through Friday
- Track real-time volumes during specific days with different weekend behavior
How it works: Configure one Sliding Window and select which days of the week to apply it. Nodinite creates independent Sliding Window evaluations for each selected day, each operating continuously throughout its respective day.
Example scenario:
Your B2B integration processes orders during business hours (Monday-Friday). You need continuous 4-hour SLA monitoring:
- Days: Monday, Tuesday, Wednesday, Thursday, Friday
- Start time: 08:00:00
- Floating span: 4 hours
- Window active from: 12:00:00 each selected day
- Error threshold: Min 10 (expect at least 10 orders every 4 hours)
On Wednesday at 3:30 PM, Nodinite evaluates Wednesday's events from 11:30 AM to 3:30 PM. On Friday at 10:15 AM, it evaluates Friday's events from 6:15 AM to 10:15 AM (once active).
Configuration: See Partial Interval Configuration for setup instructions.
Monthly Interval Monitoring
The Monthly Interval type monitors events that occur monthly, supporting both fixed dates and relative dates (like "last day of month"). This handles business processes that follow monthly cycles.
When to use Monthly Interval:
- Monitor month-end closing processes
- Track monthly invoicing or billing cycles
- Ensure monthly reports are generated
- Monitor payroll processing
How it works: You define start and end days within a month. Nodinite evaluates events that occurred between these days in the current or previous month. You can use negative values to count backwards from month-end (e.g., -1 = last day of month).
Example scenario:
Your finance team processes month-end reconciliation between the 28th and the last day of each month:
- Start day: 28
- End day: -1 (last day of month)
- Error threshold: Min 1, Max 1 (exactly one reconciliation expected)
For January 2026, Nodinite evaluates events from January 28-31. For February 2026, it evaluates February 28 (leap year considerations handled automatically).
Important: Set your search time-span to include the previous month's start date (e.g., 31.00:00:00 for at least 31 days).
Configuration: See Monthly Interval Configuration for setup instructions.
Ignore Dates
For all interval types (except Monthly Intervals), you can specify dates to ignore. This prevents false alerts during planned maintenance, holidays, or known downtime periods.
How it works:
Add repeating date patterns using placeholders:
YYYY- Any yearMM- Any monthDD- Any day
Examples:
YYYY-12-25- Ignore every Christmas DayYYYY-MM-01- Ignore the first day of every month2026-07-DD- Ignore all days in July 2026
When the current date matches an ignore pattern, Nodinite sets the resource state to OK and skips threshold evaluation.
Configuration: See Ignore Dates Configuration for setup instructions.
Alert History for Non-Events
You can analyze the frequency and pattern of Non-Event issues for root cause analysis and continuous improvement. Nodinite lets you search historical state changes for any time span, across all or individual configurations. Learn more in Add or manage Monitor View.
| Search | Resource history |
|---|---|
 Search for alert history for all resources in the Monitor View |
 Alert history for the selected configuration |
Frequently Asked Questions
Find answers to common questions and troubleshooting tips in the troubleshooting guide.
How Do I Enable Monitoring of Non-Events?
To monitor Non-Events, select the Enable monitoring checkbox for the Agent (default: checked). See the 'Configuration' user guide for details.
The screenshot below shows the remote configuration form from the Monitoring Agents administration page.
This example shows a disabled monitoring configuration.