A progress bar without a CLI to scrape
Every FFmpeg progress bar I've seen scrapes the CLI's stderr. afmpeg has no CLI to scrape, so progress had to become part of the API instead.

Every FFmpeg progress bar I've seen scrapes the CLI's stderr. afmpeg has no CLI to scrape, so progress had to become part of the API instead.

Wiring OTel-native observability through a gRPC service with a REST gateway, and discovering the gateway had split a single trace into two.

Operational telemetry can be personal data, and a web service has no first-run prompt to ask on. So plumbing is not an answer.

Two telemetries with opposite consent defaults on one OTLP layer: consent-gated analytics for a CLI, implied-consent observability for a service.

Follow one request through a Go service as a single OpenTelemetry trace in Jaeger, from the HTTP handler through the gateway and gRPC to the store.
