Audit logging on XProtect 2026 R1 with standalone integration

MIP
1

The API for audit logging (VideoOS.Platform.Log.LogClient), will it break on fresh 2026 R1 systems? It is a bit unclear to me from this information:
https://support.milestonesys.com/article/XProtect-VMS-2026-R1-OTLP-logging-scheme-compatibility-Smart-Client

We are currently only using this API with a standalone integration.

2

I would add what will happen if Customer anyway uses SC 2025R3 on stations … it will be invisible in logs? those connections?

4

In a transition phase from the old logserver to the new Open Telemetry based system, we support logging to the old system from components that have not been upgraded yet, e.g. Recording Server, Event Servers, SmartClients or MIP SDK based applications. In this case the process will be:

  1. Install 2026R1 including the new log-system. Do not uninstall the old log-server yet. Components that have not been upgraded to 2026R1 will continue to log using the old log-server

  2. When all components have been upgraded no logs will be sent to the old log-server anymore. Logs can now be migrated from the old logserver into the new system. We ship a utility for this purpose with 2026R1. The migration utility uses the Open Collector service for the migration. This means we can migrate the logs to almost any log-system that the customer might have chosen.

  3. Stop and uninstall the old logserver.