Description
If span streaming is enabled (by default in v11), let's align Node/Server behaviour with browser and always send a http.client span on outgoing requests. In practise, this should make little to no difference for servers but rather only in a "Sentry used in a script" scenario, or in heavily manually instrumented similar scenarios.
Concrete steps to take care of:
- Adjust
onlyIfParent option, to only gate http.client spans when transaction mode is enabled
- add Tests for the following scenarios:
- tracing enabled, no parent span, fetch/http request -> sends a new span
- tracing enabled, no parent span, fetch/http request -> propagates sampling decision
- tracing not set (tracing without performance), no parent span -> propagates deferred (no) sampling decision
- ensure these scenarios are also tested in browser. if not, add browser tests
Description
If span streaming is enabled (by default in v11), let's align Node/Server behaviour with browser and always send a
http.clientspan on outgoing requests. In practise, this should make little to no difference for servers but rather only in a "Sentry used in a script" scenario, or in heavily manually instrumented similar scenarios.Concrete steps to take care of:
onlyIfParentoption, to only gate http.client spans when transaction mode is enabled