15.257 14.9.17 Logs, traces y privacidad
Formato: Structured JSON or journald fields with eventName, severity, service, version, traceId?, attemptRefHash?, jobId? and errorClass.
15.257.1 Campos prohibidos
- raw frame payload
- credentials
- access token
- athlete real name
- unredacted URL query
- arbitrary stack-local tensor dump
Rotación: Size and time bounded; disk-pressure aware; critical audit events use separate quota.
15.257.2 Root spans
capture-session, attempt-analysis,
job-stage, sync-release,
deployment-activation
Sampling: Head sampling for normal operations plus tail/error retention when supported; never sample away critical domain events.
Payload: Store references and digests, not media/tensors.
Un trace facilita localizar si la latencia provino de cola, decode, GPU, IO o quality gates; no debe convertirse en un canal oculto para copiar video o datos personales.