Telemetry and logs

The server image sends nothing to Ophiolite and makes no outgoing connection of its own. It needs no Ophiolite account, subscription or licence server. The only outgoing connections are the ones you configure: an external identity provider, data sources you connect, or an OpenTelemetry collector of your own (the standard OTEL_* environment variables on the server service; off unless you set them).

Logs go to the container’s standard output (docker compose logs server). They name refusals, starts, the release and migrations; they do not contain tokens or file contents. Access decisions and changes are also recorded in the project’s activity history, which administrators see in the Workspace.

telemetry.enabled in config.json accepts only false: there is no telemetry to Ophiolite, and the field exists so that a future release cannot turn any on without a configuration change you make.