- 3 minutes to read

Troubleshooting the Nodinite Monitoring Service

Quickly resolve issues and get answers to common questions about the Nodinite Monitoring Service. This guide helps you check service status, locate installations, read diagnostics, and contact expert support.

✅ Step-by-step troubleshooting for the Nodinite Monitoring Service ✅ Visual guides to check service status and installation
✅ Direct access to diagnostics and support resources

Frequently asked questions

How do I know if the Monitoring Service has stopped?

You can easily check the state of the Monitoring Service in several places:

  1. The notification area (Status menu) of the Web Client
    Status menu in the Web Client showing the Monitoring Service state
    The notification area in the Web Client shows the current status of the Monitoring Service.
  2. From the Overview in the Administration section of the Web Client
    Monitoring Service status, URI, version, and installation path in the Administration Overview (7.10.11)
    The Administration Overview in the Web Client displays Monitoring Service status and all installed components.
  3. On the Core Services host, in IIS Manager: the Monitoring Service web site and its application pool must be started

How do I know where the Monitoring Service is installed?

Find the installation location of the Monitoring Service here:

  1. From the Overview in the Administration section of the Web Client (and all other installed components)
  2. In the Nodinite Portal, where the server and install path of the Core Services are set (Servers step → Selected server)

How do I get diagnostics for the Monitoring Service?

The Monitoring Service writes rolling diagnostic.log.json files below its installation folder. Managing the Monitoring Service shows the default path, the file format, and what the files contain. Zip the files and send them to support when you contact us. If no files are written, check that the service identity set in the Portal (Core platform services) has write rights to the folder.

Why are alerts not sent?

Check the Alarm Queue for entries that failed to send, and the retry limits in AlarmQueueSettings. A Stylesheet with embedded scripts fails unless StylesheetScriptsEnabled is true. See Common Troubleshooting Scenarios for more.

Why is Monitor Event history missing?

The Monitoring Service deletes Monitoring Events older than DaysToKeepMonitorEvents days every hour; purged events can't be restored. See Data Retention.

Contact our support

If you have questions or encounter issues with the Monitoring Service, contact our expert team, read more on the Support page.

Next Steps

Monitoring Service

Install and Update Troubleshooting

Windows Configuration

SQL Server

Administration