- 12 minutes to read

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

A Non-Events volume check goes Error when invoices stop, animated walkthrough (7.12)
Animated walkthrough: the Contoso: Invoices per day check in a Monitor View is in Error because no invoices arrived in the last day. Details shows the evaluated window, and the Log Text names the Error threshold that was not met.

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.

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, and each of its Partial and Monthly Intervals as a Resource of its own. For example, if you create 42 configurations with only a Full Interval, you monitor 42 distinct resources, each independently.

  • The Resource name is the configuration name for the Full Interval, and the interval's Display Name for a Partial Interval. A Monthly Interval is named <configuration>, Monthly Interval: '<start>:st - <end>:th'.
  • Each Resource 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 is the configuration name, so all intervals of one configuration share it.
  • The agent's own Resource, Non-Events Monitoring Agent [server], sits in the Category "Non-Events"; its Details show the run-time statistics.

Non-Events Resources in a Monitor View, in the Full Interval, Partial Interval, Monthly Interval, and ACK/NAK Categories (7.12)
You can easily view and manage all monitored Non-Event configurations in a Nodinite Monitor View.

Nodinite continuously evaluates every Non-Events configuration (as a Resource) and assigns one of the following states:

State Status Description Actions
🚫 Unavailable Resource not available You cannot evaluate 'Non-Events' due to network or security issues Review prerequisites
❌ Error Error threshold breached You detect too few or too many events 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'
Show Log View
Clear the alert
Ignore for today
⚠️ Warning Warning threshold breached You detect too few or too many events 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'
Show Log View
Clear the alert
Ignore for today
✅ OK Within user-defined thresholds
  • You keep the message count within user-defined thresholds
  • You do not perform evaluation because the start date of the evaluated interval is in the list of dates to ignore
Not applicable

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.

Contoso: Invoices per day OK with the Log Text Monitoring is currently disabled because the start day matches one of the dates to ignore (7.12)
This example shows an evaluation whose interval starts on a date in the list of dates to ignore.

Log Texts

The agent writes these Log Texts, which the Monitor View shows next to the state:

State Log Text
❌ Error / ⚠️ Warning, too few events Too few logged events occurred within the search period. The number of logged events does not meet the error threshold '5'. (the Warning text names the warning threshold)
❌ Error / ⚠️ Warning, too many events Too many events occurred within the time span. The number of logged events exceeds the error threshold ...
🚫 Unavailable, evaluation failed Could not complete the monthly evaluation. Review the diagnostics files for more information. ...
✅ OK, date ignored Monitoring is currently disabled because the start day matches one of the dates to ignore.
✅ OK, cleared Monitoring is currently disabled because the clear time is more recent than the monitoring timespan.

A custom Log Text in the Warning or Error thresholds replaces the default text.

Edit Thresholds

Fine-tune your monitoring thresholds for Non-Events in the Configuration user guide, or from the Monitor View with the Edit action in Managing Non-Events.

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 Full Interval 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.

Full Interval Example

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 Partial Interval 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.

Partial Interval Example

You process customer orders mainly between 8 AM and 6 PM on Mondays. 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 Multiple Days 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.

Multiple Days Example

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 Sliding Window 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.

gantt title Sliding Window Evaluation (4-hour window, start 8 AM) dateFormat HH:mm axisFormat %H:%M section Timeline Start Time (08:00) :milestone, 08:00, 0m Window Active (12:00) :milestone, 12:00, 0m section Evaluation Windows First eval (08:00-12:00) :active, 12:00, 0m Eval at 13:00 (09:00-13:00) :active, 13:00, 0m Eval at 14:00 (10:00-14:00) :active, 14:00, 0m Eval at 15:00 (11:00-15:00) :active, 15:00, 0m

Sliding Window Example

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

graph LR subgraph "Night (2-hour window)" A["00:00<br/>Start time"] --> B["02:00<br/>First Eval<br/>(00:00-02:00)"] end subgraph "Daytime (continuous evaluation)" B --> C["10:30<br/>Eval<br/>(08:30-10:30)"] C --> D["14:45<br/>Eval<br/>(12:45-14:45)"] end subgraph "Evening (window keeps moving)" D --> E["18:00<br/>Eval<br/>(16:00-18:00)"] end style B fill:#93d16d style C fill:#93d16d style D fill:#93d16d style E fill:#93d16d

Diagram: Using the 2-hour SLA example above (start time 00:00, floating span 2 hours), the Sliding Window moves continuously throughout the day, evaluating the 2 hours before each check. Green nodes are evaluations after the window becomes active at 02:00.

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 Sliding Window Multiple Days 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.

gantt title Sliding Window Multiple Days (Mon-Fri, 4-hour window, 08:00 start) dateFormat YYYY-MM-DD axisFormat %a %d section Week View Monday Monitoring :active, 2026-01-12, 1d Tuesday Monitoring :active, 2026-01-13, 1d Wednesday Monitoring :active, 2026-01-14, 1d Thursday Monitoring :active, 2026-01-15, 1d Friday Monitoring :active, 2026-01-16, 1d Saturday (disabled) :crit, 2026-01-17, 1d Sunday (disabled) :crit, 2026-01-18, 1d

Sliding Window Multiple Days Example

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, the window is not yet active, so Nodinite doesn't evaluate Friday's events; the first evaluation runs at 12:00 PM and covers 08:00 AM to 12:00 PM, after which the window keeps moving.

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 Monthly Interval 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). The minimum thresholds apply only once the interval's end date and time has passed.

Monthly Interval Example

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 Ignore Dates Work

Add repeating date patterns using placeholders:

  • YYYY - Any year
  • MM - Any month
  • DD - Any day

Ignore Date Examples

  • YYYY-12-25 - Ignore every Christmas Day
  • YYYY-MM-01 - Ignore the first day of every month
  • 2026-07-DD - Ignore all days in July 2026

The agent matches the pattern against the start date of the evaluated interval, not the current date. For a one-day Full Interval evaluated now, that start date is yesterday. When it matches, 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 by date and time (7.12)
Search for alert history for all resources in the Monitor View
Resource history of Contoso: Invoices per day with Error and OK entries (7.12)
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 a Non-Events configuration, check Enabled on its Basic tab in the remote configuration. See the 'Configuration' user guide for details. The Full Interval tab has its own Enabled: clear it to evaluate only the configuration's Partial and Monthly Intervals.

The screenshot below shows the remote configuration form from the Monitoring Agents administration page.
Full Interval tab of Contoso: Orders per shift with Enabled cleared and an empty Clear Date (7.12)
This configuration evaluates only its Partial and Monthly Intervals.


Next Steps