The gateway that split my trace in two
Wiring OTel-native observability through a gRPC service with a REST gateway, and discovering the gateway had split a single trace into two.
Tags
5 pages
Telemetry
The consent you can't ask for
Operational telemetry can be personal data, and a web service has no first-run prompt to ask on. So plumbing is not an answer.
Telemetry that asks, and telemetry that doesn't
Two telemetries with opposite consent defaults on one OTLP layer: consent-gated analytics for a CLI, implied-consent observability for a service.
Two telemetry events, one mangled line
O_APPEND only guarantees non-interleaved writes below PIPE_BUF, which is 4096 bytes on Linux. A fat JSONL event above that splices two lines.
Telemetry that asks first
Opt-in telemetry for a command-line tool: off until someone says yes, no personal data, a pluggable backend, and a consent flow that meets GDPR.
