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
Copy file name to clipboardexpand all lines: docs/product/sentry-basics/performance-monitoring.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,7 @@ For basic frontend or backend performance monitoring, just turn on Tracing in yo
73
73
74
74
Instead of instrumenting page loads with specific metrics at certain set intervals, like `onLoad`, `onUnload`, `onError`, etc., Sentry makes an effort to automatically instrument the libraries you rely on, providing detailed telemetry for Web Vitals, file I/O, network requests, and more. This lets you see the performance impact of every request, and any errors that occur during that request.
75
75
76
-
This differs substantially from other performance monitoring tools that only capture *predefined* metrics with much less granularity. All your holistic metrics in Sentry are backed up by the raw tracing data, so you can drill into any specific request or operation to get a detailed view of its performance
76
+
This differs substantially from other performance monitoring tools that only capture *predefined* metrics with much less granularity. All your holistic metrics in Sentry are backed up by the raw tracing data, so you can drill into any specific request or operation to get a detailed view of its performance.
77
77
78
78
These performance metrics are sent by the Sentry SDK as part of each [Span](/concepts/key-terms/tracing/#whats-a-span), which is the smallest unit of work in a [Trace](/concepts/key-terms/tracing/). Traces are assembled in Sentry's backend, and then extrapolated to populate all the tools we have for monitoring performance.
0 commit comments