- 10 minutes to read

Release Notes

Non-Events Configuration

Info
This guide teaches how to configure the Nodinite Non-Events Monitoring Agent to get number-based alerts from Non-Events Monitoring configurations based on the Logging result from Nodinite Log Views.

There are two different types of configurations for Non-Events Monitoring available:

Non-Events (this page) - Monitoring based on the number of rows from a search operation on a Nodinite Log View.
ACK/NAK - Monitoring based on a correlation using a grouped Nodinite Log View.

Non-Events

The Non-Events tab holds an array with one or more Non-Event configurations.

Here's an example of the Non-Events configuration tab.

Click the Add button to add a new Non-Events configuration.

Add a Non-Events Monitoring configuration.
Then, expand the accordion.
Repeat this step as necessary.

Basic Tab

In the Basic tab, you provide the essential information about the Non-Events configuration.

Here's an example of a Non-Events configuration, there is one accordion per configuration entry.

Enabled - When checked, this Non-Event configuration is enabled.
Name - The user-friendly display name for this specific Non-Event configuration.
Description - The user-friendly description for this specific Non-Events configuration.
Log View API URI - Determines which 'Log View' to use. Copy and paste the URI from the 'Copy API URI' dialogue in the Log View.

Copy the address from a Log View; the button is available after performing a search.

To use the URL with a Non-Events Monitoring configuration, do a search, then click the 'Copy API URL' button within a Nodinite Log View.

Info
The system generates the URL, you may need to tune it according to your actual IIS environment. If the agent is installed on the same server as Nodinite Core Services, try http://localhost/... instead.

Search time-span - Determines how far back in time to perform the search for 'Full interval' and 'Partial interval' evaluations. Format (days.hours:minutes:seconds, e.g. 7.12:34:56)
- A Full Interval configuration makes use of all the data in the result.
- You can define many Partial Interval configurations using a sub-set of the data in the result.
- You can define many Monthly Interval configurations using a sub-set of the data in the result
  Note
  The value must at least span the start date of the previous month, e.g. 31.00:00:00

Important
If the Log View has a Time Interval Configuration, it must allow for a detailed time search and perform the actual search NOT using one of the pre-defined time intervals.

Time Interval Configuration

Full interval tab

Apply the rules for the entire interval (search time-span) from within the Full Interval tab.

Here's an example of the Non-Events 'Full Interval' tab.

Enable 'Full Interval' evaluation - When checked, the Monitoring of the 'Full Interval' configuration is enabled.

Here's an example of a Disabled 'Full Interval' Non-Events configuration.
Ignore this date - When set, the Monitoring is disabled for the remainder of that day. A User in the Nodinite Web Client can update this field by issuing a 'Clear the alert' Remote Action from a Monitor View with the Resource.

Warning (Full interval)

Warning - Min - The minimum number of expected events. If the number of events is lower than the specified value, a Warning alert is raised.
Warning - Max - The maximum number of expected events. If the number of events is higher than the specified value, a Warning alert is raised.
Warning - Log Text -The log text to display when raising the warning instead of the default log text.

Error (Full interval)

Error - Min - The minimum number of expected events. An Error alert is raised if the number of events is lower than the specified value.
Error - Max - The maximum number of expected events. An Error alert is raised if the number of events exceeds the specified value.
Error - Log Text - The log text to display on the Resource when raising the Error alert instead of the system default log text.

Partial Intervals tab

You can add one or more Partial Intervals to monitor. A partial interval should span the same or less time than the Full interval.

Here's an example of the Non-Events Partial Intervals tab.

Each partial interval has a name and its own independent configuration. Partial intervals can intersect one another.

Click the Add button to add a Non-Events Partial Interval configuration.

Here's an example of how to add a Partial Interval Monitoring configuration.
Then, expand the accordion.

Display Name - Display Name for the interval, if not set, the name will be set like: [Auto generated name: Interval: 'Monday 08:00:00 - Monday 16:59:59']
Note
If you leave the field empty, Nodinite will automatically change the Resource name of the 'Display Name' according to the current configuration.
Ignore this date - When set, Monitoring is disabled for the remainder of the day. The User can update this field by issuing a 'Clear the alert' Remote Action.

Important
Modifications to the 'Display Name' or configuration may change Resource's name. If you pinpoint individual Non-Events Resources by name, review your Monitor Views after changing the configuration on 'Partial Intervals' to ensure they are included in the Monitoring!

Next, there are two more tabs with additional properties to configure:

Interval Tab

A Non-Events Partial Interval configuration can filter the result on the result from the search operation using an interval configuration.

Here's an example of an Interval configuration for a Partial Interval Non-Events configuration.

Partial interval type - Choose the interval type to use in the Monitoring for this partial interval.

Here's an example of the different interval types you can use to limit the sub-set of data to include in the Monitoring.

Partial Interval Type	Description	Comment
Default	Evaluates the whole interval	To evaluate the entire interval, the current time of day must have passed the end date/time.
Multiple Days	Same as the Default option repeated for the selected days.
Sliding Window	Evaluate the events in a sliding window (Floating)	Monitoring is Active when the current time of day has passed the Start Date/Time + the Floating time span since the latter must have passed to evaluate the interval.
Sliding Window - Multiple Days	Same as the Floating option repeated for the selected days.

Start day - Select a start day for the interval.
Start time - Time of day. Format (hours:minutes:seconds, e.g. 10:10:00).
End day - Select an end day for the interval.
End time - Time of day. Format (hours:minutes:seconds, e.g. 13:37:42).

Thresholds tab

You set the number-based Monitoring from witin the Thresholds tab:

Here's an example of 'Thresholds' tab for configuring a Non-Events Partial Intervals configuration.

Warning (Partial interval)

Warning - min - The minimum number of expected events. If the number of events is lower than the specified value, a Warning alert is raised.
Warning - max - The maximum number of expected events. If the number of events is higher than the specified value, a Warning alert is raised.
Warning - Log Text - The log text to display when raising the warning instead of the default log text.

Error (Partial interval)

Error - min - The minimum number of expected events. An Error alert is raised if the number of events is lower than the specified value.
Error - max - The maximum number of expected events. An Error alert is raised if the number of events exceeds the specified value.
Error - Log Text - The log text to display when raising the error instead of the default log text.

Monthly Intervals tab

A Monthly Interval is designed to deal with business transactions that occur each month, not necessarily on a specific date but within a defined range.

Important
The 'Search time-span' must be set to a value that includes the start date of the previous month.

The Monthly Intervals tab holds an array with one or more configurations.

Here's an example of the Non-Events 'Monthly Intervals' tab.

Click the Add button to add a new configuration.

Add a Non-Events 'Monthly Interval' Monitoring configuration.
Then, expand the accordion.
Repeat this step as necessary.

Interval Tab (Monthly Interval)

In the Interval tab, you configure the range and the Monitoring thresholds.

Start day - Select the start day in the month for the interval. You may also use negative values like -1, for the last day of the month.
End day - Select the end day of the month for the interval. You may also use negative values, like -1, for the last day of the month, and so on.

Thresholds tab (Monthly Interval)

In the Thresholds tab, the number-based properties are configured:

Here's an example of the 'Thresholds' tab for configuring a 'Monthly Interval'.

Warning (Monthly interval)

Warning - min - The minimum number of expected events. If the number of events is lower than the specified value, a Warning alert is raised.
Warning - max - The maximum number of expected events. If the number of events is higher than the specified value, a Warning alert is raised.
Warning - Log Text - The log text to display when raising the warning instead of the default log text.

Error (Monthly interval)

Error - min - The minimum number of expected events. An Error alert is raised if the number of events is lower than the specified value.
Error - max - The maximum number of expected events. An Error alert is raised if the number of events exceeds the specified value.
Error - Log Text - The log text to display when raising the error instead of the default log text.

Ignore dates tab

You can add one or more repeating dates to ignore in the Monitoring.

Ignore dates does not apply to 'Monthly Intervals'.
Click the Add button to add one (or more) dates to ignore:

Here's an example of the Ignore dates tab for Non-Events.
Then, expand the accordion.
Repeat this step as necessary.

Example	Description
YYYY	Replace the current year
MM	Replace the current month
DD	Replace the current day

Note
The starting date of any Non-Events configuration is ignored if logged events occur/start on those days that match the configuration.

Scheduling Tab

This topic is in details here (shared page between Non-Events and ACK/NAKs).

Authentication tab

You can apply an impersonation configuration if the service account running the Non-Events Monitoring Agent does not have access rights to the Log View.

Tip
We recommend that you create a Non-Events role of which the service account running the Non-Events Monitoring Agent is a member and add this role to all Log Views to include in the Non-Events Monitoring. If you do this, the impersonation configuration is not needed.

Use Impersonation - Check this checkbox to impersonate the call to the Log View. By default, the account running the Non-Events Monitoring Agent is used.

If you check this checkbox, (*) will be visible in the Authentication tab. This indicates that the Non-Events configuration is using a configuration with impersonation.

Enter the credentials for the account with access rights to the Log View.

Next Step

Scheduling - Set a period in between to limit the frequency of the calls. This is an important setting you should consider applying on all configurations! Otherwise, you may stress the system to the point where Nodinite becomes unresponsive.
Add or manage a Monitoring Agent Configuration
Add or manage Monitor View

Configuration
Install Nodinite Non-Events Monitoring Agent
Monitoring Agents
Applications

Explore Nodinite for 30 days – completely free

See how Nodinite resolves your technical issues, in a

LIVE Demo!