Markdown

Observability acceptance record

Use with Observability for LLM apps.

SignalDiagnostic purposeSource/versionAccess boundaryRetention/deletionResponse owner
Request outcomeDistinguish held from delivered
Model metadataAttribute configuration, usage and latency
Retrieval metadataIdentify eligible source/version decisions
Validation resultSeparate schema from evidence support
Missing telemetryDetect exporter/buffer failures

Raw payload collection needs a separate justified purpose, approved data scope and controls. Pseudonymous IDs remain sensitive where re-identification is possible. Moving data to cold storage is not deletion.

Acceptance probes

Record expected versus observed results, configuration, date, remaining gaps and owner. The article’s incident is invented; replace it with your own measured evidence before claiming implementation acceptance.