---
title: "Tracing"
description: "Learn how to enable tracing in your app and discover valuable performance insights of your application."
url: https://docs.sentry.io/platforms/unity/tracing/
---

# Set Up Tracing | Sentry for Unity

With [tracing](https://docs.sentry.io/product/insights/overview.md), Sentry is able to [connect events coming from different parts of your game](https://docs.sentry.io/platforms/unity/usage/automatic-error-capture.md#connecting-errors-captured-on-different-layers), whether it's native plugins or a backend. It helps you debug hard problems that involve C# scripts as well as the native layer on all platforms. It also allows you to monitor your game's performance, measuring metrics like initialization time, time spent on scene loading, and ANRs. Besides connecting different errors together, 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](https://docs.sentry.io/product/sentry-basics/tracing/distributed-tracing.md).

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.

## [Configure](https://docs.sentry.io/platforms/unity/tracing.md#configure)

First, enable tracing and configure the sample rate for transactions. Set the sample rate for your transactions by either:

* Setting a uniform sample rate for all transactions using the `TracesSampleRate` option in your SDK config to a number between `0` and `1`. (For example, to send 20% of transactions, set `TracesSampleRate` to `0.2`.)
* Controlling the sample rate based on the transaction itself and the context in which it's captured, by providing a function to the `TracesSampler` config option.

The two options are meant to be mutually exclusive. If you set both, `TracesSampler` will take precedence.

```csharp
// Add this to the SDK initialization callback
// Example uniform sample rate: capture 100% of transactions
options.TracesSampleRate = 1.0;
```

Learn more about tracing [options](https://docs.sentry.io/platforms/unity/configuration/options.md#tracing-options), how to use the [TracesSampler](https://docs.sentry.io/platforms/unity/configuration/sampling.md#setting-a-sampling-function) function, or how to [sample transactions](https://docs.sentry.io/platforms/unity/configuration/sampling.md#sampling-transaction-events).

## [Verify](https://docs.sentry.io/platforms/unity/tracing.md#verify)

Test out tracing by starting and finishing a transaction, which you *must* do so transactions can be sent to Sentry. Learn how in our [Custom Instrumentation](https://docs.sentry.io/platforms/unity/tracing/instrumentation/custom-instrumentation.md) content.

While you're testing, set `TracesSampleRate` to `1.0`, as that ensures that every transaction will be sent to Sentry. Once testing is complete, you may want to set a lower `TracesSampleRate` value, or switch to using `TracesSampler` to selectively sample and filter your transactions, based on contextual data.

## [Next Steps](https://docs.sentry.io/platforms/unity/tracing.md#next-steps)

* #### [Instrumentation](https://docs.sentry.io/platforms/unity/tracing/instrumentation.md)

  Learn how to instrument tracing in your app.

* #### [Trace Propagation](https://docs.sentry.io/platforms/unity/tracing/trace-propagation.md)

  Learn how to connect events across applications/services.

## Pages in this section

- [Instrumentation](https://docs.sentry.io/platforms/unity/tracing/instrumentation.md)
- [Trace Propagation](https://docs.sentry.io/platforms/unity/tracing/trace-propagation.md)