- 6 minutes to read

Configuring the Nodinite Non-Events Monitoring Agent

Unlock proactive, self-service monitoring with the Nodinite Non-Events Monitoring Agent. This guide empowers you to configure remote settings, set up flexible alerts, and fine-tune monitoring for your business needs—all from a single, intuitive interface.

✅ Gain real-time, proactive alerts for missing or delayed business events
✅ Leverage remote configuration for rapid, secure setup and management
✅ Empower administrators and business users with self-service monitoring
✅ Streamline integration with flexible agent settings and best practices

You will learn how to configure the Nodinite Non-Events Monitoring Agent to deliver timely, actionable alerts based on results from Nodinite Log Views.

Info

To enable monitoring and remote configuration, first install and create the initial Monitoring Agent Configuration for the Non-Events Monitoring Agent. If you're new, start here.

Remote Configuration

As a Nodinite Administrator, click the 'Configuration' button to open a modal and configure the agent.
Remote Configuration
Click the 'Configuration' button to open the configuration dialog for the agent.

You can also apply specific configurations directly on the Resource using the Action button, provided your Monitor View has the Remote Actions feature enabled.

Add New Configuration

You can add and manage two types of Non-Events Monitoring configurations, each designed for different monitoring scenarios:

  • Non-Events – 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-Event configurations
Example of the two types of Non-Event configuration available.

Settings Tab

Within the Settings tab, define key details that determine how the Non-Events Monitoring Agent operates.

Settings Tab
Settings tab for configuring environment, debug, and culture information.

To Save, click a suitable button. Save options
Example of the Save options for configuration changes.

Note

The delay in presenting the new evaluated state depends on the synchronization interval set for the monitoring agent. Click the Sync Now button to force an immediate synchronization.

Save and close – Save and close the dialog.
Cancel – Close the dialog without saving changes.

Environment

Set the name of the target Environment (e.g., TEST, QA, PROD) to align with your business context. This is a common feature for all Monitoring Agents.

Debug

Enable or disable the Debug flag for additional file logging as needed. By default, this is unchecked. This setting is shared across all Monitoring Agents.

Culture Information

The Culture Information setting controls how time-based data from this agent appears in the Web Client and Web API.

Authentication Tab

The Authentication tab configures how the Non-Events Monitoring Agent authenticates when calling Nodinite Log Views through the Web Client APIs.

Info

Available from version 6.5.0.0 and later. OAuth 2.0 / OIDC authentication support requires Nodinite v7 with OpenID Connect configured. For earlier versions, use impersonation only.

OAuth 2.0 / OIDC Authentication

When Nodinite v7 is configured to use an Identity Provider (IDP) with OAuth 2.0 / OIDC, the Non-Events agent must provide additional authentication information to access Log Views.

Authentication Tab - OAuth Protected
The Authentication tab with OAuth 2.0 / OIDC authentication enabled.

The following fields configure OAuth 2.0 authentication:

Field Description Required Notes
Protected Checkbox to enable OAuth 2.0 / OIDC authentication Conditional Check this when Nodinite v7 uses OAuth 2.0 / OIDC mode. When checked, Client Credential Grant flow authenticates API calls
Client ID Public identifier for your application (issued by IDP) Conditional Required when Protected is checked. The client must have permissions to access Log View APIs
Client Secret Confidential key for application authentication Conditional Required when Protected is checked; keep this secure and never commit to version control
Scope Space-separated list of access permissions Conditional Required when Protected is checked (e.g., api://nodinite-webapi/.default)
IDP Token Endpoint URL where authentication requests are sent Conditional Required when Protected is checked; this is where the agent obtains access tokens

Follow these guidelines when configuring OAuth 2.0 authentication:

  • Enable Protected mode only when Nodinite v7 is configured with an Identity Provider (Azure AD, Entra ID, or other OIDC-compliant IDP)
  • The Client ID and Client Secret must be registered with your IDP and granted permissions to access Nodinite Web API resources
  • For Azure AD (Entra ID), see the Install Nodinite v7 - OpenID Connect guide for complete IDP registration and configuration
  • The Scope format depends on your IDP configuration—for Azure AD, use api://<client-id>/.default format
  • The IDP Token Endpoint must be accessible from the server running the Non-Events Monitoring Agent
  • Keep Client Secret values secure—store them in the Nodinite Configuration Database (encrypted at rest)

Example OAuth 2.0 configuration for Azure AD (Entra ID):

  • Protected: Checked
  • Client ID: 12345678-1234-1234-1234-123456789abc (from your app registration)
  • Client Secret: your_secure_client_secret (from your app registration)
  • Scope: api://nodinite-prod-webapi/.default
  • IDP Token Endpoint: https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token

Warning

Upgrading from Nodinite v6 to v7 with OAuth? After upgrading to v7 with OpenID Connect enabled, you must update all Non-Events configurations with OAuth 2.0 credentials. Until updated, the agent cannot authenticate API calls and monitoring will fail. See the Upgrading from v6 to v7 guide for complete migration instructions.

Impersonation (Windows Authentication Mode Only)

Note

Impersonation applies to Windows authentication mode only. When Nodinite v7 uses OAuth 2.0 / OIDC, authenticate using the Client Credentials (Client ID and Client Secret) configured above instead of impersonation.

Impersonation allows the agent to authenticate as a specific user account when the service account running the Non-Events Monitoring Agent lacks access to required Log Views.

Tip

Best practice for Windows authentication: Create a dedicated Non-Events role with access to all monitored Log Views and assign it to the service account. This approach is more secure than impersonation and simplifies credential management.

Impersonation is configured per Non-Events or ACK/NAK configuration—see the configuration-specific authentication sections:

Add Non-Events Monitoring Agent Configuration

After you install the Non-Events Monitoring Agent, provide Nodinite with connection details so the Monitoring Service can recognize the new agent.

No monitoring or configuration of the Non-Events Monitoring Agent is possible until you complete the steps below.

Configuration Steps

  1. Add and configure a new Monitoring Agent Configuration.
    • Connection information is available in the README.txt file in the installation folder.
  2. Use the Remote Configuration feature to configure the agent (see the beginning of this guide).
  3. Create one or more self-service enabled Monitor Views that include the selected Resources provided by the Non-Events Monitoring Agent to match your business needs.
  4. Fine-tune specific settings directly on Resources using Remote Actions.

Next Step

Scheduling – Set a period in between to limit the frequency of the calls. This is an important setting that you really 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

Install Nodinite Non-Events Monitoring Agent
Monitoring Agents
Applications