feat(develop): Add outgoing_request context

[mydea]

This should replace event.request on the client completely.

Draft on top of #13203

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
develop-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 2, 2025 2:41pm

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
changelog	⬜️ Ignored (Inspect)	Visit Preview		Apr 2, 2025 2:41pm
sentry-docs	⬜️ Ignored (Inspect)	Visit Preview		Apr 2, 2025 2:41pm

[cleptric]

We do not store query parameters this way. https://develop.sentry.dev/sdk/expected-features/data-handling/#spans

[mydea]

Ah, I based this on https://develop.sentry.dev/sdk/data-model/event-payloads/request/#attributes:

url Optional. The URL of the request if available. The query string can be
declared either as part of the url, or separately in query_string.

We can split it out for sure!

[bruno-garcia]

This should replace event.request on the client completely.

if the product will have UX based in the new outgoing request field (which makes sense) could we have something in Relay that moves event.request to the new field when we know it's a client event? the heuristics to be defined (sdk name? other fields etc)

this way older sdks can have the benefits added by the new field

[mydea]

This should replace event.request on the client completely.

if the product will have UX based in the new outgoing request field (which makes sense) could we have something in Relay that moves event.request to the new field when we know it's a client event? the heuristics to be defined (sdk name? other fields etc)

this way older sdks can have the benefits added by the new field

The idea is that today we have this overloaded thing - you can't even really set this outgoing_request information as of now for server SDKs, because event.request is already used for the incoming request information. So I do not think it will really be possible to extract this, as we can't easily differentiate what kind of data is stored in event.request 🤔