Observability

Export a safe subset of Arc0 audit events as OpenTelemetry logs and inspect delivery health.

Launch and Scale

Available on the Launch and Scale plans. See pricing.

Arc0 exports audit events as OTLP JSON logs over HTTPS. Configure a collector destination with the Arc0 operator, then enable its assigned destination in your project. Export requires an active Launch or Scale entitlement, checked again when a delivery runs.

Exported fields

Each log contains the event timestamp and type, the event ID, the resource ID, and the project ID. The service name is arc0 and the instrumentation scope is arc0.audit.

Arguments, tool results, credentials, HTTP headers and arbitrary audit metadata are excluded. There is no payload-export switch. Traces, metrics, gRPC and configurable resource attributes are planned extensions; they are not part of the current export.

Configure a destination

The operator registers the collector's HTTPS URL and authentication in Arc0's API service, bound to your organization. Project administrators enable or disable that assigned destination. Your collector must accept OTLP JSON log requests at the configured URL, including any required OTLP HTTP logs endpoint path. Arbitrary URLs or authentication headers cannot be supplied by an agent.

The HTTPS transport rejects private and reserved addresses, verifies TLS, refuses redirects, and times out after 10 seconds. IPv6-only collectors are not supported yet.

Delivery health

Audit events enter a durable delivery queue in the same transaction as the original audit record. Failures retry with backoff for up to eight attempts. Diagnostics expose pending and failed counts and the last successful delivery time. They do not expose authentication secrets or response bodies.

Disabling a destination stops subsequent dispatches; a request already in flight may finish. A plan downgrade prevents further paid exports. Delivery is at least once, so use arc0.event.id to deduplicate when your collector requires it.

On this page