Incidents are easier to investigate when you can see what happened inside your HTTP service: which route failed, how long it took, and what the request looked like.
But logging request data can create new problems. Passwords and tokens may end up in logs. Large payloads can consume memory. And if telemetry export waits on a slow or unavailable backend, it can affect the request path.
To address these tradeoffs, I built safe-http-telemetry, an open-source Rust crate for Axum and Tower applications.
Its design goal is to make HTTP telemetry useful while keeping capture, resource use, and export behavior under the application’s control.
Three design priorities
Redact sensitive data before queueing When an application captures request data, it needs to consider credentials such as passwords, bearer tokens, and API keys.
safe-http-telemetry applies capture limits and redaction before events enter the export queue.…