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
Bring the JS SDK `BrowserTracing` integration options up to date with the currently available options:
* add `finalTimeout` option introduced in v7
* remove `maxTransactionDuration` option dropped in v7
* improve `idleTimeout` description
Copy file name to clipboardExpand all lines: src/platforms/javascript/common/performance/instrumentation/automatic-instrumentation.mdx
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ Supported options:
52
52
53
53
### tracingOrigins
54
54
55
-
A list of strings and regular expressions. The JavaScript SDK will attach the `sentry-trace` and `baggage` headers to all outgoing XHR/fetch requests whose destination contains a string in the list or matches a regex in the list. If your frontend is making requests to a different domain, you'll need to add it there to propagate the `sentry-trace` and `baggage` headers to the backend services, which is required to link transactions together as part of a single trace.
55
+
A list of strings and regular expressions. The JavaScript SDK will attach the `sentry-trace` and `baggage` headers to all outgoing XHR/fetch requests whose destination contains a string in the list or matches a regex in the list. If your frontend is making requests to a different domain, you'll need to add it there to propagate the `sentry-trace` and `baggage` headers to the backend services, which is required to link transactions together as part of a single trace.
56
56
57
57
**The `tracingOrigins` option matches against the whole request URL, not just the domain. Using stricter regex to match certain parts of the URL ensures that requests do not unnecessarily have the additional headers attached.**
58
58
@@ -76,10 +76,16 @@ This function can be used to filter out unwanted spans such as XHR's running hea
76
76
77
77
### idleTimeout
78
78
79
-
The idle time, measured in ms, to wait until the transaction will be finished. The transaction will use the end timestamp of the last finished span as the endtime for the transaction.
79
+
The idle time, measured in ms, to wait until the transaction will be finished, if there are no unfinished spans. The transaction will use the end timestamp of the last finished span as the endtime for the transaction.
80
80
81
81
The default is `1000`.
82
82
83
+
### finalTimeout
84
+
85
+
The maximum duration of the transaction, measured in ms. If the transaction duration hits the `finalTimeout` value, it will be finished.
86
+
87
+
The default is `30000`.
88
+
83
89
### startTransactionOnLocationChange
84
90
85
91
This flag enables or disables creation of `navigation` transaction on history changes.
@@ -92,12 +98,6 @@ This flag enables or disables creation of `pageload` transaction on first pagelo
92
98
93
99
The default is `true`.
94
100
95
-
### maxTransactionDuration
96
-
97
-
The maximum duration of a transaction, measured in seconds, before it will be marked as "deadline_exceeded". If you never want transactions marked that way, set `maxTransactionDuration` to 0.
98
-
99
-
The default is `600`.
100
-
101
101
### markBackgroundTransactions
102
102
103
103
This option flags transactions when tabs are moved to the background with "cancelled". Because browser background tab timing is not suited for precise measurements of operations and can affect your statistics in nondeterministic ways, we recommend that this option be enabled.
0 commit comments