Source
APM, tracing & profiling — found from sitemap — BugSnag
Checked for BugSnag on 6 Nov 2026
- Page
- https://docs.bugsnag.com/performance/distributed-tracing/error-linking/
- Checked
- 6 Nov 2026, 04:22 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:36a82ef429894abb30fd4a24fe88a2ac8a01e1b82065f6a26d0e9582c2a17295
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Error trace navigation Report an error
“You can navigate from the error to the relevant distributed trace with just one click in your BugSnag dashboard.”
-
Handled errors only Report an error
“Typically, if an app crashes then performance data will not be sent before the app terminates. Therefore you will only usually see linked traces for handled errors.”
-
SDK requirement Report an error
“To link errors with distributed traces you need to use both BugSnag Error and BugSnag Performance SDKs.”
-
Automatic linking Report an error
“With the exception of JavaScript and React Native (described below), the two SDKs automatically link their data when supported versions of the SDKs are used.”
-
Supported platforms Report an error
“Android bugsnag-android v6.6.0 bugsnag-android-performance v1.4.0”
-
Expo versions Report an error
“Expo. bugsnag-expo v54.0.0 bugsnag-expo-performance v54.0.0”
-
Flutter versions Report an error
“Flutter bugsnag-flutter v4.0.0 bugsnag-flutter-performance v1.1.0”
-
Ios versions Report an error
“iOS bugsnag-cocoa v6.30.1 bugsnag-cocoa-performance v1.6.0”
-
React native versions Report an error
“React Native bugsnag-js v8.06.0 bugsnag-js-performance v2.8.0”
-
Unity versions Report an error
“Unity bugsnag-unity v8.2.0 bugsnag-unity-performance v1.6.0”
-
Web versions Report an error
“Web bugsnag-js v8.0.0 bugsnag-js-performance v2.8.0”
-
Js manual config Report an error
“The JavaScript and React Native SDKs require a manual configuration step to link their data. As part of the Basic configuration of the Performance SDK, pass in the bugsnag field with a reference to the BugSnag Error client”
-
Manual correlation metadata Report an error
“If you are using a different OTel-compliant SDK or a version of the BugSnag Error SDK not supporting error linking, you can combine performance and error data manually by setting the active trace and span ID in the metadata of error events.”
-
Manual snippet languages Report an error
“NodeJS Java dotNET Python Go Ruby”
Scores citing this record
- The Agency Tech Lead Error capture, grouping & triage
- The Agency Tech Lead APM, tracing & profiling
- The Data Protection Officer Error capture, grouping & triage
- The Data Protection Officer APM, tracing & profiling
- The Mobile Team Lead Error capture, grouping & triage
- The Mobile Team Lead APM, tracing & profiling
- The SaaS CTO Error capture, grouping & triage
- The SaaS CTO APM, tracing & profiling
- The Skeptic Error capture, grouping & triage
- The Skeptic APM, tracing & profiling
- The Site Reliability Engineer Error capture, grouping & triage
- The Site Reliability Engineer APM, tracing & profiling