Uninstall Log API
The Nodinite Log API is part of the Nodinite Core Services, so it is removed together with them, never on its own. Do this when you start over during an installation or update, or when you decommission an environment. The full procedure is Uninstall Nodinite v7; this page lists what matters for the Log API.
Before You Uninstall
- Stop or repoint every sender. Log Agents, the Pickup Service, and your own code that post to the Log API base URL
https://{host}:{port}/LogAPI/can no longer deliver Log Events. Log Agents and the Pickup Service keep their events and retry until a Log API is available again. - Decide whether to keep the databases. The Log API writes to the Configuration Database and the Log Databases; keep them if you plan to reinstall and continue with the same data.
Remove the Log API
Run the CLI from an elevated PowerShell 7 prompt in the extracted ZIP bundle root, as described in Uninstall commands:
uninstallremoves the Core Services, including the Log API IIS web site, but not the agents.teardown-environmentremoves the agents first and then the Core Services; use it to remove a complete environment.--delete-databasesalso drops the databases; see Remove Database Option. This deletes all logged data.
Cleanup That Applies to the Log API
From After Uninstallation - Optional Cleanup:
- IIS Application Pool Cleanup for the Log API site.
- Windows Service Accounts and Permissions for the Log API service account, including its SQL Server logins.
- Certificate Cleanup and Firewall and Network Cleanup for the Log API port.
- Azure AD (Entra ID) Cleanup when the Log API was protected with OAuth 2.0: remove the logApi app registration and the logging client registrations from Protect the Log API with OAuth 2.0 and Entra ID.
To confirm the removal, check that the Log API web site is gone from IIS Manager and that https://{host}:{port}/scalar no longer answers.
Note
Nodinite v6 is no longer supported. To move an existing v6 installation, follow Updating from v6 to v7.