feat(develop): Add outgoing_request context
#13204
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
| { | ||
| "contexts": { | ||
| "outgoing_request": { | ||
| "url": "https://sentry.io/api/0/projects/sentry/sentry/issues/?page=1", |
There was a problem hiding this comment.
We do not store query parameters this way. https://develop.sentry.dev/sdk/expected-features/data-handling/#spans
There was a problem hiding this comment.
Ah, I based this on https://develop.sentry.dev/sdk/data-model/event-payloads/request/#attributes:
urlOptional. 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!
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 |
This should replace `event.request` on the client completely.
mydea
force-pushed
the
fn/add-outgoingRequestContext
branch
from
2ede4a0 to
8d37afa
Compare
This should replace
event.requeston the client completely.Draft on top of #13203