- 5 minutes to read

Manage Non-Events Interval Scheduling

Take control of your monitoring schedules and boost system performance with Nodinite Non-Events Interval Scheduling. This feature empowers both technical and business users to fine-tune how often Non-Events monitoring runs, minimizing risk and disruption to mission-critical services—all from a flexible self-service portal.

What you’ll achieve with Nodinite Interval Scheduling:

✅ Optimize performance and reduce system stress with tailored monitoring intervals
✅ Empower your teams to manage schedules without IT intervention
✅ Minimize risk and avoid unnecessary load on business-critical systems
✅ Ensure compliance and transparency with full self-service control

Add interval schedules to control how often the Nodinite Non-Events Monitoring Agent runs. Achieve better performance and reduce system stress.

Nodinite lets your team and business users manage all or individual ACK/NAKs Non-Events monitoring configurations through a flexible self-service portal. This powerful feature helps you minimize risk and disruption to mission-critical services, while giving you full control.

graph LR subgraph "Log Views in the Monitoring" roLV1(fal:fa-search Acknowledged Orders before 8:00
At least 100 with no more than 2 in each group) roLV2(fal:fa-search Daily exchange rates before 06:00
Verify at least one) roLV3(fal:fa-search Any other Log View) end subgraph "Non-Event Configurations" roNES(fal:fa-calendar-alt Schedules) --> | Run every hour on weekdays | roLV1 roNES --> | Run daily every 15 minutes, active between 02:00 and 06:00 | roLV2 roNENS(fal:fa-calendar-circle-exclamation No schedule) --> | fal:fa-redo Runs frequently according to the polling interval
TRY TO AVOID THIS SETUP - Add a schedule! | roLV3 end

Diagram: This mermaid diagram shows how you can use interval schedules in Nodinite to optimize monitoring and reduce unnecessary load. Each configuration demonstrates a real-world scheduling scenario, helping you visualize the impact of smart scheduling on system performance.

Scheduling Tab

Assign one or more schedules to all Non-Events Categories. If schedules overlap, the system runs queries according to the combined schedule. Each schedule enforces a minimum interval between monitoring attempts, so you use resources efficiently.

Add Schedule

Use the Scheduling tab to manage interval schedules and control how often each Non-Events configuration runs.

Scheduling tab
Here's an example of the Scheduling tab from the Remote Configuration.

Click the Add button to create a new Interval Schedule.

Add Interval Schedule
Use the Add button to add a new Interval Schedule.

Expand the accordion to manage essential information about this configuration.

Essential Information

Each interval schedule includes the following fields, which the system administrator sets:

Manage Interval Schedule
Expanded accordion showing essential interval schedule details.

  • Display Name – Enter a unique name for the schedule (required)
  • Interval between queries – Enter the TimeSpan format (day.shours:minutes:seconds, e.g., 0.00:05:00) to limit monitoring frequency (required)
  • Schedule type – Choose the evaluation type for this schedule

Schedule Type

Choose from the following schedule types:

  • Single range – Run the query only between the specified start and end time
  • Multiple days – Run the query between the specified start and end time on selected days

Single Range

Select Single range to run the query only between the specified start and end time.

Single range

  • Start day – Select the start day (Monday–Sunday)
  • Start time – Enter the time of day (hours:minutes:seconds, e.g., 10:10:00)
  • End day – Select the end day (Monday–Sunday)
  • End time – Enter the time of day (hours:minutes:seconds, e.g., 13:37:42)

Multiple Days

Select Multiple days to run the query between the specified start and end time on selected days.

Multiple Days

Check which days to run:

  • Monday – The system evaluates on Mondays
  • Tuesday – The system evaluates on Tuesdays
  • Wednesday – The system evaluates on Wednesdays
  • Thursday – The system evaluates on Thursdays
  • Friday – The system evaluates on Fridays
  • Saturday – The system evaluates on Saturdays
  • Sunday – The system evaluates on Sundays
  • Start time – Enter the time of day (hours:minutes:seconds, e.g., 10:10:00)
  • End time – Enter the time of day (hours:minutes:seconds, e.g., 13:37:42)

Statistics

Click the Details Actions menu-item of the Resource in the Non-Events Category to open the statistics modal.
Details Actions menu-item

A modal displays information about the current configuration.
Statistics
This example shows run-time statistics for the current non-Events monitoring configuration.

  • Make sure queries run quickly (<10 seconds each). Add filters to the Log View or limit the lookback period to improve performance and reduce system stress.
  • If you experience performance issues, contact our support team. We appreciate seeing these statistics and screenshots of your current configurations.

Frequently Asked Questions

Can I schedule the Non-Events agent to run only on specific calendar days of the month — for example, day 5, or days 5–7, between 12:00 and 18:00?

This is a common requirement when an integration only processes data on fixed calendar days each month (for example, a month-end file drop on the 5th).

Current capability: Interval Scheduling controls time-of-day windows and days of the week (Monday–Sunday). It does not natively support "run only on calendar day 5 of the month" or "run on days 5–7 of each month."

Monitor Calendar Days with a Monthly Interval

If your goal is to verify that the expected events arrive on specific calendar days of the month, use a Monthly Interval configuration instead of a schedule. Set Start day to 5 and End day to 7 (or both to 5 for a single day) in the Monthly Intervals tab. The Monthly Interval evaluates events by calendar day, not by weekday, so it doesn't drift as the calendar shifts. It doesn't restrict the time of day, so combine it with an interval schedule if you also want to limit when the agent queries.

Workaround with a Weekday-based Schedule

If you need the agent itself to run only on those days, and the target calendar days predictably fall on the same day(s) of the week — or if you are willing to accept a small margin — combine these settings:

  1. Use Multiple Days to select only the weekday(s) that typically correspond to the dates in your monthly cycle.
  2. Set Start time to 12:00:00 and End time to 18:00:00 to restrict execution to the 12:00–18:00 window.
  3. Set the Interval between queries to a value like 0.01:00:00 (every hour) so it checks regularly within that window, but never outside it.

Important

Limitation: Because the Gregorian calendar shifts weekdays each month, a weekday-based schedule will occasionally fire on the wrong dates or miss the intended dates. This approach is therefore a best-effort workaround, not a guaranteed calendar-day solution.

For a precise calendar-day schedule, contact Nodinite Sales or Support to discuss this as a feature requirement. Providing details about your use case helps prioritize this capability in future releases.

Next Steps

Manage Monitoring
Configuration of the agent

Prerequisites
Monthly Interval Monitoring