- 2 minutes to read

Update the Nodinite Monitoring Service

The Nodinite Monitoring Service is part of the Nodinite Core Services and is updated with them; you don't update it on its own. Follow Updating Nodinite v7: select the environment in the Nodinite Portal, download and extract the ZIP, and run the CLI workflow in an elevated PowerShell 7 prompt.

What You Set for the Monitoring Service in the Portal

An update uses the settings stored for the environment in the Portal. Change them there before you download the package if needed:

Setting Where in the Portal
Environment to update Step 1: Basics → Register the environment
Monitoring Service port and service identity Step 4: Servers → Core platform services
TLS host name and certificate Step 4: Servers → Core host Configuration

What the Update Does for the Monitoring Service

Your System Parameters, Monitor Views, Alarm Plugins configuration, and the Alarm Queue are stored in the Configuration Database and are kept.

Tip

Test the update in a non-production environment first, and schedule a Maintenance Mode window so that operators expect the short monitoring gap.

Verify the Monitoring Service

  1. Check that the Monitoring Service web site and application pool are started in IIS Manager.
  2. In the Web Client, check the Monitoring Service state in the Status menu and the Monitoring Agents in Administration.
  3. Check the Alarm Queue for alerts that failed during the update.

Note

Nodinite v6 is no longer supported. To move an existing v6 installation, follow Updating from v6 to v7.

Next Steps

Updating Nodinite v7
Managing the Monitoring Service

Core Services
Install Monitoring Service
Monitoring Service
Prerequisites
Troubleshooting
Uninstall Monitoring Service