Update the Nodinite Log API
The Nodinite Log API is updated together with the other Nodinite Core Services: you select the environment in the Nodinite Portal, download a new ZIP, and run the CLI workflow. The full procedure is Updating Nodinite v7; this page lists what matters for the Log API.
What You Can Change for the Log API in the Portal
Change these values in the Portal before you download the update, never in IIS or in the settings files:
| Setting | Where in the Portal |
|---|---|
| Log API port and service account | Step 4: Servers › Core platform services |
| TLS host name and certificate | Step 4: Servers › Core host Configuration |
| Enable Authentication and Audiences (OAuth 2.0 only) | Step 2: Auth › Log API |
Warning
If you change the Log API port or host name, update the Log API base URL in every Log Agent and in the Pickup Service. If you turn on Enable Authentication, every logging client must send a bearer token first; see Protect the Log API with OAuth 2.0 and Entra ID.
Run the Update
- Select the environment in the Portal.
- Download and extract the ZIP.
- Run the CLI workflow (validate, dry-run,
deploy-environment) from an elevated PowerShell 7 prompt. The CLI updates the Log API IIS web site together with the other Core Services.
While the Log API is being updated it cannot accept Log Events. Log Agents and the Pickup Service keep their events and send them when the Log API is back; that is why asynchronous logging is recommended. Code that calls the Log API directly must retry on its own.
If the CLI reports locked files, see File Locks Detected.
Verify the Log API After the Update
- Open Scalar at
https://{host}:{port}/scalarand check that the Log API operations are listed. - Post a test Log Event to
https://{host}:{port}/LogAPI/api/LogEvent/Validate; see Log using REST. - Check that new Log Events from your Log Agents and the Pickup Service appear in a Log View.
Note
Nodinite v6 is no longer supported. To move an existing v6 installation, follow Updating from v6 to v7.