HTTP acceptance does not prove telemetry retention

An HTTP success response from a client telemetry endpoint proves only that the application accepted the payload. When forwarding is asynchronous, the event may still be queued, retried, or dropped. Incident tooling should distinguish accepted, queued, delivered, retried, and dropped states, and readiness checks should exercise the delivery path rather than only confirm that configuration exists.

A missing query result is not by itself a delivery failure: verify query coverage, labels, time bounds, and retention. For diagnostics that cannot be reconstructed elsewhere, use bounded durable summaries or explicit delivery and drop metrics instead of assuming best-effort logs form an audit trail.