Traces

Ingestion over the SDK, HTTP and OTLP, the explorer, redaction and capture policy, sampling and backpressure, retention, export and deletion.

• IngestionHow a batch of spans reaches a project over the HTTP API, what is checked before anything is stored, and what the receipt says.
• OpenTelemetrySending OTLP/HTTP traces to a project, how GenAI semantic-convention attributes are mapped onto EvalBook spans, and what the adapter does with content, environments and schema versions.
• ExplorerSearching traces, reading a trace and its spans, error groups, the live tail and saved views, and which capability each of them needs.
• Redaction and captureThe project's capture policy — full, redacted or metadata-only — applied to every body before it is stored, the path and pattern rules, where redaction is recorded, and what an external judge may see.
• Sampling and backpressurePer-trace sampling policies by environment, the plan's daily span allowance, per-minute backpressure, and the counters that keep every drop and refusal visible.
• Retention, export and deletionRetention per content class with purge receipts and tombstones, JSONL trace exports with a manifest and digest, and deletion requests that remove every derived row and withdraw exports.