Operations | Monitoring | ITSM | DevOps | Cloud

Trace redaction permanently removes sensitive data from your traces, for when something like an API key ends up in a span attribute. Tempo 3.0 could do it, but only from a list of trace IDs, so you had to go find every affected trace first. In Tempo 3.1 you can hand it a TraceQL query instead. Separately, trace-by-ID got a filter. You normally ask for a trace and get all of it. Now you can pass a TraceQL query and get back only the spans that match.

In honor of World Space Week, we're spotlighting Jackson Sweeney's story and his role in Blue Ghost Mission 1. As a Thermal Engineer at Firefly Aerospace, he used Grafana to ensure that the spacecraft maintained the right temperature throughout the mission... and receive a Golden Grot Award for his use case. Behind every successful moonshot are people solving one hard problem after another. For engineers like Jackson, that means turning an extraordinary ambition into thousands of practical decisions.

Use Sentry tracing to investigate three different problems in one shopping flow: an N+1 query, an expired promo-code warning, and a checkout exception. The entire shopping flow happens through the agent conversation on Empower Plant’s homepage: a search for plants under $200, adding one of each to the cart, starting checkout, applying SAVE20, then attempting to place the order. The trace connects that flow to repeated database queries and an N+1 issue, a warning that SAVE20 has expired, and a checkout exception with its inventory-validation stack trace.