Requests proxied via YARP are missing in the traces

[saithis]

Package

Sentry

.NET Flavor

.NET

.NET Version

8.0.0

OS

Any (not platform specific)

SDK Version

4.13.0

Self-Hosted Sentry Version

No response

Steps to Reproduce

1. Create a ASP.NET Core project
2. Add Sentry.AspNetCore and wire it up (.UseSentry + config)

"Sentry": {
        "Dsn": "...",
        "IncludeActivityData": true,
        "MaxRequestBodySize": "None",
        "TracesSampleRate": 1.0
    },

3. Add Yarp.ReverseProxy
4. configure a route, that just echos the request back
5. configure a route, that takes the request and forwards it to the echo route via YARP (in production it would be another api for us, but for local debugging i tested it with the echo endpoint)
6. call the route via postman/etc.

Expected Result

The proxied request should show up in the trace as a child

Actual Result

It doesn't

[bruno-garcia]

Is the proxy forwarding all headers? I imagine that might be the culprit.

Doesn't sound like a Sentry issue tbqh, there's something added in the middle that must be aware of headers and propagate them.

If the proxy is .NET, and runs Sentry, for example Sentry.AspNetCore, our SDK does the propagation automatically.

[Marioo1357]

@saithis When it started not work for you? From .Net 9 update or Sentry release?

[saithis]

@bruno-garcia YARP should be forwarding all headers, yes. Our app is .NET 8, uses Sentry via Sentry.AspNetCore and uses the YARP nuget package for proxying the requests.

@Marioo1357 We just started using Sentry and I'm just trying to get it to work properly. We had no previous version with sentry. Also, we didn't update to .NET 9 yet, still on .NET 8.

I tried it with Sentry.OpenTelemetry now. It shows the missing traces then, but some things appear twice:

Seems like every http.client request is recorded via Sentry.AspNetCore and via Sentry.OpenTelemetry

[bruno-garcia]

@jamescrosswell is the duplicated span when adding Sentry.OTel a known issue?

[jamescrosswell]

@jamescrosswell is the duplicated span when adding Sentry.OTel a known issue?

It's not. @saithis how are you initializing Sentry and OpenTelemetry?