Ktor client: HTTP span shows the redirect’s status instead of the final response #6346

Integration

other

Java Version

17

Other Error Monitoring Solution

No

Other Error Monitoring Solution Name

No response

Version

8.61.0

Steps to Reproduce

Integration: sentry-ktor-client 8.61.0, Ktor client 3.0.0 (Java engine)

1. Set up a server where /start returns 302 to /fail, and /fail returns 500 after a short delay.
2. Make a request to /start with a Ktor client that uses SentryKtorClientPlugin (redirects are followed by default), inside a transaction.
3. Look at the trace in Sentry: the http.client span is ok and much shorter than the request, even though a “HTTP Client Error with status code: 500” event is captured
4. Repeat with waitForChildren = true on the transaction and call finish() while the request is in flight: the transaction is sent before the 500 comes back.

Example from my own test org: https://kismeow.sentry.io/explore/traces/?end=2026-10-21T23%3A59%3A59&field=id&field=span.name&field=span.description&field=span.duration&field=transaction&field=timestamp&field=span.status&project=-1&start=2026-10-21T00%3A00%3A00&utc=true

Expected Result

The span stays open for the whole redirect chain, then gets the final response's status and is passed to beforeSpan once before it's closed.

Actual Result

When a request made with SentryKtorClientPlugin gets redirected, the HTTP span is closed as soon as the redirect comes back, not when the final response arrives.

For a request that goes 302 → 500:

• The span is marked ok, even though the request ended with a 500 (the 500 error event is still captured).
• The span's duration covers only the redirect response, so it looks much faster than it really was.
• beforeSpan is called for every response in the redirect chain. The second call gets a span that’s already closed.
• If the transaction waits for its child spans (waitForChildren), it gets sent right after the redirect, before the request is actually done.