On this page
Maintain data and review logs¶
Find evidence in the service logs¶
From the installation’s Compose command, keep the project and file flags
and replace up and its arguments.
ps -ashows services that exited, includingmigrateandassets.logs --tail=100 web worker beatshows recent application output. For a failed one-shot step, inspect its own service log.
Before restarting, record the service, timestamp and operation, request or task ID.
The shipped long-running Compose services use the json-file driver
with rotation at 10 MB and up to five files per container. A new logging
policy applies on container recreation. Export support evidence before
it rotates or a rollout recreates the containers. Volume data and
application-level retention have separate controls.
Ordinary observers can collect operational events. Core also exposes a distinct query trace extension contract. Trace data can include protected query or execution fields according to the extension and grants. Restrict trace access and export only a reviewed subset suitable for the recipient. See extension contracts for the integration boundaries.
Manage changes to indexes and storage¶
Before switching a space’s embedding model, index configuration or vector backend, record the current setup and check provider and storage readiness. A previously stored vector cannot be compared correctly with a new model’s output just because their dimensions match. Confirm the planned rebuild on a representative space and query sample. For an attached corpus, coordinate with its owner and follow storage connections before changing external data. When a release requires a fresh pass or a migration, follow its release instructions and verify search and citations with a known corpus afterward.
Keep an eye on storage and retention. Beat schedules bounded work for query-log aggregation and retired managed pgvector data. The vector sweep starts in discovery mode. Enabling deletion changes persistent data. Prepared payload and stale graph reclamation are separate opt-in operations with authority checks. Before enabling any reclamation, verify the candidates, the reader versions and your recovery point. Use the delivery reference and reclamation procedures for the exact commands, prerequisites and limits.