- 5 minutes to read

How to monitor the Nodinite Product Key

Stay ahead of license issues and ensure uninterrupted access to Nodinite by proactively monitoring your product key status. This guide shows you how to configure the Nodinite Web Service Monitoring Agent to validate your product key and receive timely alerts before expiration.

✅ Instantly detect when your Nodinite product key is about to expire
✅ Automate license monitoring and compliance
✅ Receive actionable alerts and maintain continuous service

This guide provides instructions for configuring the Nodinite Web Service Monitoring Agent to validate the Nodinite product key (License).

graph TD A[Web Service Configuration] --> |Evaluate Nodinite Product Key| B{Is Valid?} B -->|Yes| E[OK] B -->|No| F[Error]
*Diagram: The Web Service Monitoring Agent evaluates the Nodinite Product Key. If valid, the state is OK; if not, an error is triggered.*

The Nodinite Web Service Monitoring Agent enables you to monitor if your product key (Trial or Rental) is about to expire by evaluating the body of the HTTP/HTTPS response from a call to the Nodinite Web API.

The Web Service configuration you create will become a Resource in one or more Monitor Views where you can track the evaluated state in real time:
Valid License
Product Key is valid and has not yet expired or is not about to expire any time soon.

Invalid License
Product Key is about to expire.

In this case, you must update the ProductKey system parameter to continue using the Web Client.

You can get an updated product key by:

  • Contacting your partner/reseller if applicable
  • Getting a new key from the Nodinite portal
  • Contacting our technical support support

Step 1: Add a new Application

Logically identify and group monitored Resources using the Applications feature. Manage these in the Applications tab for your selected instance of the Nodinite Web Service Monitoring Agent.

  • Click the Add button
    Add new Application
    Add a new Application for grouping monitored resources.

  • Enter Name and a unique id. For example, use Nodinite as Name and 1337 as the unique Id. You can use any unique values.
    Nodinite as Application
    Example of Nodinite as an Application.

Step 2: Add a new Web Service Monitoring Configuration

Configure what to monitor—in this case, the Nodinite Web API.

  • Click the Add button
    Add new Web Service
    Add a new Web Service for license monitoring.

  • Expand the empty entry by clicking on the accordion
    Expand empty entry
    Expand to configure your new Web Service.

Step 3: Basic tab

Name your configuration by editing the following fields in the Basic tab:

Basic Tab
Configure the basic settings for license monitoring.

  • Make sure the configuration is enabled (checked)
  • Set the Display name to a logical name, e.g., Evaluate Nodinite Product Key
  • Set the Description to provide context, e.g., Use the Nodinite Web Service Monitoring Agent to get an alert when the Nodinite product key is about to expire or has already expired
  • Select the Application you created in Step 1

Step 4: Advanced tab

Manage your time-related thresholds in the Advanced tab:
Advanced Tab
Set polling intervals, timeouts, and retry logic for robust monitoring.

  • Set the Polling Interval (e.g., 3600 seconds for infrequent checks)
  • Set the Request Timeout (e.g., 120 seconds)
  • Check Allow Retries
  • Set the Number of retries (e.g., 3) to avoid false alerts
  • Set the Retry Status Code to OK to ignore errors during retries

Step 5: Request tab

Configure the actual Request in the Request tab:
Request Tab
Define the request details for the Nodinite Web API.

  • Enter the URI to the Web API, e.g., http://localhost/Nodinite/Dev/WebAPI/api/status (replace DEV as appropriate). Use localhost if the Web Service agent is installed on the same server as the Web API.
  • Set the method to Get

Leave the rest of the fields empty. The Web API is not SOAP and does not require additional HTTP headers.

Step 6: Response tab

Configure response validation in the Response tab:
Response Tab
Set expected status codes and response validation criteria.

  • Set the Status Code to 200 (OK)
  • For this type of check, you can usually leave performance checkboxes unchecked

Step 7: Evaluate response body tab

Configure evaluation of the HTTP response body in the Evaluate response body tab:
Evaluate response body
Use RegEx Match to detect license expiration warnings in the response.

  • Select Expression Type: RegEx Match
  • Enter the following Expression:
^(?>(?:[^k]+|k+(?!ey expires))*)$

This matches if the phrase 'key expires' is part of the response.

Leave the rest of the fields at their default values.

Step 8: Certificate tab

If you have performed Hardening of your Nodinite installation, you may want to receive alerts for certificate issues as well. Configure this in the Certificate tab:
Certfificate tab
Monitor certificate validity and enforce secure connections.

  • Check Evaluate certificate if you use a certificate
  • Set the number of days before expiry for Warning and Error alerts
  • Check Force the use of certificate if you want to enforce certificate usage
  • Leave Allow connection for invalid certificates unchecked to ensure security

Step 9: Authentication tab

If the Web API application pool account is not the same as the Windows Service account running the Nodinite Web Service Monitoring Agent, provide alternate credentials in the Authentication tab:
Authentication tab
Configure Windows Authentication if required.

  • Check Use Windows Authentication
  • Enter the Domain User: DOMAIN\user (User must have access to the Nodinite Web Client)
  • Enter the Password for the user

Step 10: Save configuration

Click Save to persist your configuration. You should see a success message:
Save success
Confirmation of successful configuration save.

Step 11: Create a Monitor View and Configure alerts

Configure a Monitor View and select an Alarm Plugin to receive alerts in your preferred way. These steps are detailed in the Add or manage Monitor View user guide.

Make sure to select the Resource you named in step 3.


Next Step

Add or manage Monitor View
Add or manage a Monitoring Agent Configuration

Monitoring Agents
Monitor Views
Administration