FAQ: Troubleshooting the Non-Events Monitoring Agent
Quickly resolve Non-Events monitoring issues with Nodinite. This FAQ gives you actionable troubleshooting tips, performance optimization strategies, and answers to common questions—empowering your team to maintain a healthy, high-performing monitoring environment.
✅ Get expert troubleshooting tips for common Non-Events issues
✅ Optimize performance and avoid unnecessary alerts
✅ Access direct support and best practices for configuration
✅ Empower your team with actionable insights
If you cannot resolve an issue, contact our Support or email support@nodinite.com for expert help.
Frequently Asked Questions
| FAQ | Question | Quick Answer |
|---|---|---|
| FAQ1 | How do I configure AckNak correlation when Request/Response use different fields? | Use Search Field Expressions to normalize correlation keys |
| FAQ2 | How do I monitor that at least 1 invoice arrives on each working day (Mon–Fri)? | Use one configuration with 5 Partial Interval (Default) entries, one per weekday |
Quick Troubleshooting Tips
Why does my Partial Interval with 00:00:00 → 23:59:59 never alert on a missing minimum count?
This is a common misconfiguration when using the Partial Interval – Multiple Days type to monitor daily business transactions such as invoice uploads.
The Problem
When you configure a Partial Interval with:
- Start time:
00:00:00 - End time:
23:59:59 - Days checked: Monday, Tuesday, Wednesday, Thursday, Friday
- Search time-span: e.g.
6.23:59:59
…you create a window that covers the entire calendar day. Nodinite only evaluates a Partial Interval after the end time has passed. Because 23:59:59 is the very last second of the day, the evaluation for a minimum threshold can only trigger once the day is already over — at which point it is already the next day.
In Practice
- A maximum threshold still works correctly — the moment too many events are detected during the day, Nodinite triggers the alert immediately.
- A minimum threshold (e.g. "at least 1 invoice per day") effectively never alerts during business hours. The alert would only fire in the first seconds after midnight, when the business day it refers to is already gone.
Warning
Configuring a Partial Interval that spans the full day (
00:00:00–23:59:59) with a minimum threshold is an ineffective configuration for detecting missing events during the working day.
The Correct Solution – One Configuration with 5 Partial Intervals
Create one Non-Event configuration and add 5 Partial Interval (Default) entries inside it — one for each weekday. On the Basic tab, set the search time-span to 7.00:00:00 (7 days) so the lookback window always covers the full previous week. Each partial interval then evaluates the whole interval for its specific day.
| Partial Interval name | Start day | Start time | End day | End time |
|---|---|---|---|---|
| Monday check | Monday | 00:00:00 |
Monday | 23:59:59 |
| Tuesday check | Tuesday | 00:00:00 |
Tuesday | 23:59:59 |
| Wednesday check | Wednesday | 00:00:00 |
Wednesday | 23:59:59 |
| Thursday check | Thursday | 00:00:00 |
Thursday | 23:59:59 |
| Friday check | Friday | 00:00:00 |
Friday | 23:59:59 |
Why Does This Work?
Each partial interval targets a single named day. Nodinite evaluates it after 23:59:59 on that day, checking whether the minimum threshold was met across the whole day window. Because only one day is in scope per partial interval, the evaluation is unambiguous and fires correctly once the day has passed.
Thresholds Per Partial Interval
- Warning minimum:
1 - Error minimum:
1 - Maximum:
-1for no limit (unless you also want to cap the volume, then set the maximum threshold as needed)
Info
This approach creates 5 resources in your Monitor View — one per partial interval. You can group them under the same Category (e.g. "Invoice Upload – Daily") to keep your monitor overview tidy.
Warning
Leave the Full Interval tab with no configuration and the Monthly Intervals tab empty. Adding entries there would create additional, unintended evaluations alongside your partial interval checks.
Tip
Use Ignore Dates to skip public holidays so you do not receive false alerts on days your business does not operate.
Why do I get many alerts even though nothing appears in the associated Log Views?
To ensure reliable monitoring, make your Log Views run quickly—ideally in under 10 seconds. If you configure many Non-Event monitors with slow Log Views, you risk overloading your system, which leads to timeouts, deadlocks, and other performance issues.
- Optimize your Log Views to run fast (<10 sec).
Review the Statistics to gain insights into performance and scheduling intervals.
Visualize performance statistics for your Non-Events Monitoring Agent. - Set a higher, more reasonable interval instead of syncing with the agent every 60 seconds.
- Use a schedule to control how often queries run and reduce system load.
How do I add Non-Events configurations to Nodinite monitoring?
Add Non-Events configurations in Nodinite easily and flexibly. If you have the right access, you can add as many configurations as your business requires. Just follow the steps in the Configuration user guide.
Info
You must belong to the Administrators role to manage the Configuration.
Next Step
- Configuration – Set up your Non-Events monitoring configurations.
- Partial Intervals Tab – Add and configure partial interval entries for your monitoring.
Related Topics
- Monitoring Non-Events – Understand how interval types and state evaluation work.
- Partial Interval – Multiple Days – Learn the behaviour difference that causes this misconfiguration.
- Partial Interval (Default) – Understand how the Default type evaluates the whole interval.
- AckNak Correlation Troubleshooting – Resolve AckNak correlation configuration issues.