Skip to content

Commit 5fc3c4e

Browse files
add period
Co-authored-by: Alex Krawiec <[email protected]>
1 parent 1ae8485 commit 5fc3c4e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/product/sentry-basics/performance-monitoring.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ For basic frontend or backend performance monitoring, just turn on Tracing in yo
7373

7474
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.
7575

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.
7777

7878
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.
7979

0 commit comments

Comments
 (0)