Non-Events Configuration
Unlock proactive, number-based monitoring from the Logging with Nodinite! This guide shows you how to configure Non-Events monitoring using Log Views, set up flexible thresholds, and leverage advanced features for seamless integration and business insight.
✅ Proactively detect missing or delayed business-critical messages
✅ Set up flexible, number-based alerting for any scenario
✅ Leverage Log Views and advanced intervals for precise monitoring
✅ Empower your business with step-by-step configuration and best practices
This guide walks you through configuring the Nodinite Non-Events Monitoring Agent to deliver number-based alerts from Non-Events Monitoring configurations, using results from Nodinite Log Views.
Nodinite offers two powerful configuration types for Non-Events Monitoring:
- Non-Events (this page) – Monitor based on the number of rows from a search operation on a Nodinite Log View.
- ACK/NAK – Monitor based on correlation using a grouped Nodinite Log View.
Non-Events
Use the Non-Events tab to manage one or more Non-Event configurations for precise, number-based monitoring.
This image shows the Non-Events configuration tab.
- Click the
Add
button to create a new Non-Events configuration.
This image shows how to add a new Non-Events Monitoring configuration. - Expand the accordion to reveal configuration details.
- Repeat these steps for multiple configurations.
Basic Tab
In the Basic tab, enter essential details for your Non-Events configuration.
This image shows a Non-Events configuration—one accordion per entry.
- Enabled – Activate or deactivate this Non-Event configuration.
- Name – Enter a user-friendly display name.
- Description – Add a clear description for this configuration.
- Log View API URI – Specify which 'Log View' to use. Copy and paste the URI from the 'Copy API URI' dialog in the Log View.
Copy the address from a Log View after you perform a search.
This image shows how to copy the API URL from a Nodinite Log View for use in your Non-Events configuration.
Info
:The system generates the URL, but you may need to adjust it for your IIS environment. If you run the agent on the same server as Nodinite Core Services, use
http://localhost/...
instead.
- Search time-span – Define how far back to search for 'Full interval' and 'Partial interval' evaluations. Use the format days.hours:minutes:seconds (e.g., 7.12:34:56).
- Full Interval uses all data in the result.
- Partial Interval lets you define multiple sub-intervals.
- Monthly Interval supports monthly business cycles.
Note
Set the value to at least span the start date of the previous month, e.g.,
31.00:00:00
.
Important
:Ensure the Log View's Time Interval Configuration allows detailed time searches and does not use pre-defined intervals.
Full Interval Tab
Apply rules for the entire interval (search time-span) in the Full Interval tab.
This image shows the Non-Events 'Full Interval' tab.
- Enable 'Full Interval' evaluation – Activate monitoring for the full interval.
This image shows a disabled 'Full Interval' Non-Events configuration. - Ignore this date – Temporarily disable monitoring for the day. Users can update this field by using a 'Clear the alert' Remote Action in a Monitor View.
Warning (Full Interval)
- Warning - Min – Set the minimum expected events. The system triggers a Warning alert if the value is lower.
- Warning - Max – Set the maximum expected events. The system triggers a Warning alert if the value is higher.
- Warning - Log Text – Enter custom log text for warnings.
Error (Full Interval)
- Error - Min – Set the minimum expected events. The system triggers an Error alert if the value is lower.
- Error - Max – Set the maximum expected events. The system triggers an Error alert if the value is higher.
- Error - Log Text – Enter custom log text for errors.
Partial Intervals Tab
Add one or more Partial Intervals to monitor sub-intervals within the main time span. You can configure each interval independently and allow them to overlap.
This image shows the Non-Events Partial Intervals tab.
- Click the
Add
button to create a Partial Interval configuration.
This image shows how to add a Partial Interval Monitoring configuration. - Expand the accordion for details.
- Display Name – Enter a name for the interval. If you leave this blank, Nodinite auto-generates one.
Note
If you leave this blank, Nodinite updates the Resource name based on the configuration.
- Ignore this date – Disable monitoring for the day. You can update this via a Remote Action.
Important
:If you change the 'Display Name' or configuration, Nodinite may alter the Resource's name. If you reference Resources by name, review your Monitor Views after changes to ensure continued monitoring.
Next, configure the Interval and Thresholds tabs for each Partial Interval.
Interval Tab
Filter results using interval settings.
This image shows an Interval configuration for a Partial Interval.
- Partial interval type – Choose the interval type for this Partial Interval.
This image shows different interval types for flexible monitoring.
Partial Interval Type | Description | Comment |
---|---|---|
Default | Evaluates the whole interval | Current time must have passed the end date/time. |
Multiple Days | Same as Default, repeated for selected days. | |
Sliding Window | Floating window evaluation | Active when current time passes Start Date/Time + floating span. |
Sliding Window - Multiple Days | Floating window, repeated for selected days. |
- Start day – Select the start day.
- Start time – Enter the start time (hh:mm:ss).
- End day – Select the end day.
- End time – Enter the end time (hh:mm:ss).
Thresholds Tab
Set number-based monitoring thresholds for each Partial Interval.
This image shows the 'Thresholds' tab for Partial Intervals.
Warning (Partial Interval)
- Warning - min – Set the minimum expected events. The system triggers a Warning alert if the value is lower.
- Warning - max – Set the maximum expected events. The system triggers a Warning alert if the value is higher.
- Warning - Log Text – Enter custom log text for warnings.
Error (Partial Interval)
- Error - min – Set the minimum expected events. The system triggers an Error alert if the value is lower.
- Error - max – Set the maximum expected events. The system triggers an Error alert if the value is higher.
- Error - Log Text – Enter custom log text for errors.
Monthly Intervals Tab
Monitor business transactions that occur monthly, not always on a specific date.
Important
:Ensure the 'Search time-span' includes the start date of the previous month.
Use the Monthly Intervals tab to add one or more configurations.
This image shows the Non-Events 'Monthly Intervals' tab.
- Click the
Add
button to create a new configuration.
This image shows how to add a Monthly Interval Monitoring configuration. - Expand the accordion for details.
- Repeat as needed.
Interval Tab (Monthly Interval)
Configure the range and thresholds for monthly monitoring.
- Start day – Select the start day (negative values like -1 mean last day of the month).
- End day – Select the end day (negative values allowed).
Thresholds Tab (Monthly Interval)
Set number-based thresholds for monthly intervals.
This image shows the 'Thresholds' tab for Monthly Intervals.
Warning (Monthly Interval)
- Warning - min – Set the minimum expected events. The system triggers a Warning alert if the value is lower.
- Warning - max – Set the maximum expected events. The system triggers a Warning alert if the value is higher.
- Warning - Log Text – Enter custom log text for warnings.
Error (Monthly Interval)
- Error - min – Set the minimum expected events. The system triggers an Error alert if the value is lower.
- Error - max – Set the maximum expected events. The system triggers an Error alert if the value is higher.
- Error - Log Text – Enter custom log text for errors.
Ignore Dates Tab
Add one or more repeating dates to ignore in monitoring.
Ignore dates do not apply to 'Monthly Intervals'.
Click the
Add
button to add dates to ignore.Expand the accordion for details.
Repeat as needed.
Example | Description |
---|---|
YYYY | Replace the current year |
MM | Replace the current month |
DD | Replace the current day |
Note
:If you log events on the starting date of any Non-Events configuration, the system ignores that date.
Scheduling Tab
Learn more about scheduling in this guide (shared for Non-Events and ACK/NAKs).
Authentication Tab
Apply impersonation if the service account running the Non-Events Monitoring Agent lacks access to the Log View.
Tip
:Create a dedicated Non-Events role for the service account and add it to all Log Views you want to monitor. This approach often eliminates the need for impersonation.
- Use Impersonation – Check this option to impersonate the call to the Log View. By default, the agent's account is used.
If you check this option, (*)
appears in the Authentication tab, indicating impersonation is active.
Enter credentials for the account with Log View access rights.
Next Step
Scheduling – Set a period to limit call frequency. This step is crucial to prevent system overload and keep Nodinite responsive.
Add or manage a Monitoring Agent Configuration
Add or manage Monitor View
Related Topics
Configuration
Install Nodinite Non-Events Monitoring Agent
Monitoring Agents
Applications