Update the Nodinite Logging Service
The Nodinite Logging Service is updated together with the other Nodinite Core Services; it has no separate update. You select the environment in the Nodinite Portal, download the new package, and run the CLI workflow in elevated PowerShell 7, as described in Updating Nodinite v7:
- Select the environment in the Portal (what an environment is).
- Download and extract the ZIP.
- Run the CLI workflow: validate, dry-run, deploy.
What You Can Change for the Logging Service
An update applies the current Portal values for the environment. To change how the Logging Service is hosted, change the value in the Portal before you download the package:
| Setting | Portal step |
|---|---|
| Logging Service port, or its own service account | Step 4: Servers – Core platform services |
| Shared service account for all Core Services | Step 2: Auth – Service account defaults |
| TLS host name and certificate subject | Step 4: Servers – Core host Configuration |
Portal settings that an update applies to the Logging Service.
Logging Service behaviour (retention, Log Databases, message processing) is set with System Parameters; an update keeps their values, and changing them needs neither an update nor a restart. A new service account needs the SQL Server rights in the Logging Service Prerequisites.
Verify the Logging Service After the Update
- The CLI deploy finishes without errors. If it reports locked files, see File Locks Detected.
- In IIS Manager, the Logging Service web site and its application pool are started.
- In the Web Client, the Logging Service shows as running in the Administration Overview.
- New Log Events are processed and show up in Log Views.
Tip
Test the update in a non-production environment first.
Note
Nodinite v6 is no longer supported. To move an existing v6 installation, follow Updating from v6 to v7.