You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifies whether this SDK should send events to Sentry. Defaults to `true`. Setting this to `enabled: false` doesn't prevent all overhead from Sentry instrumentation. To disable Sentry completely, depending on environment, call `Sentry.init` conditionally.
440
+
Specifies whether this SDK should send events to Sentry. Defaults to `true`. Setting this to `enabled: false` doesn't prevent all overhead from Sentry instrumentation. To disable Sentry completely, depending on environment, call `Sentry.init` conditionally.
441
441
442
442
</ConfigKey>
443
443
@@ -595,6 +595,18 @@ An optional property that configures which downstream services receive the `sent
An optional property that controls which downstream services receive tracing data, in the form of a `sentry-trace` and a `baggage` header attached to any outgoing HTTP requests.
601
+
602
+
The option may contain a list of strings or regex against which the URLs of outgoing requests are matched.
603
+
If one of the entries in the list matches the URL of an outgoing request, trace data will be attached to that request.
604
+
String entries do not have to be full matches, meaning the URL of a request is matched when it _contains_ a string provided through the option.
605
+
606
+
If <PlatformIdentifiername="trace-propagation-targets" /> is not provided, trace data is attached to every outgoing request from the instrumented client.
@@ -605,7 +617,6 @@ An optional property that configures which downstream services receive the `sent
605
617
606
618
An optional property that configures which features are in experimental mode. This property is either an `Object Type` with properties or a key/value `TypedDict`, depending the language. Experimental features are still in-progress and may have bugs. We recognize the irony.
0 commit comments