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/platforms/javascript/common/tracing/index.mdx
+26-15Lines changed: 26 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -6,23 +6,22 @@ sidebar_order: 4000
6
6
7
7
With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
You can additionally <PlatformLinkto="/profiling">set up Profiling</PlatformLink> to get even more detailed tracing information like stack traces and flame graphs.
If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
@@ -65,6 +64,18 @@ While you're testing, set <PlatformIdentifier name="traces-sample-rate" /> to `1
65
64
66
65
If you leave your sample rate at `1.0`, a transaction will be sent every time a user loads a page or navigates within your app. Depending on the amount of traffic your application gets, this may mean a lot of transactions. If you have a high-load, backend application, you may want to consider setting a lower <PlatformIdentifiername="traces-sample-rate" /> value, or switching to using <PlatformIdentifiername="traces-sampler" /> to selectively sample and filter your transactions, based on contextual data.
See <PlatformLinkto="/tracing/instrumentation/automatic-instrumentation">Automatic Instrumentation</PlatformLink> to learn about all the things that the SDK automatically instruments for you.
71
+
</PlatformSection>
72
+
73
+
## Custom Instrumentation
74
+
75
+
You can also manually start spans to instrument specific parts of your code. This is useful when you want to measure the performance of a specific operation or function.
76
+
77
+
See <PlatformLinkto="/tracing/instrumentation/custom-instrumentation">Custom Instrumentation</PlatformLink> to learn how to manually start spans.
0 commit comments