Operations
This page covers audit behavior, configuration deployment, and secrets.
Startup and scheduling
The service validates its configuration and checks both OT Backup and the selected maintenance-system provider before workers start. Workers run immediately after startup and then wait for their configured interval after each completed run. Runs do not overlap.
Audit logging
Synchronization writes Maintenance system synchronization to the OT Backup
integration audit endpoint only when at least one item was created, changed, or
removed. Details include created, changed, removed, and failure counts. A run
containing only failures does not write this summary.
Each claimed alert is completed individually. The alert worker writes a
Maintenance system alert processing summary only when at least one work order
was created. Details include processed, created-work-order, and failure counts.
These audit summaries are separate from the service's Serilog file. A successful provider request does not prove that a later OT Backup audit request was accepted.
Configuration loading
Configuration files are loaded in this order; later files override earlier files:
appsettings-common.jsonbeside the executableappsettings-common.<environment>.jsonappsettings-common.<machine>.jsonappsettings.jsonappsettings.<environment>.jsonappsettings.<machine>.jsonappsettings.<user>.json
Only the two base files are required. Put server-specific settings in a protected machine override using the exact Windows machine name.
Secrets and TLS
The OT Backup and provider credentials are separate. Keep them out of source control, logs, screenshots, tickets, and handover notes. Use service URIs whose TLS certificates are trusted by the service host; do not disable certificate validation.
The checked-in Serilog file path is
../Logs/Maintenance.Integration/serilog.log.