---
title: "Tracing"
description: "Learn how to enable tracing in your app using the Sentry Ruby SDK and see where requests, jobs, and agent runs fail or slow down."
url: https://docs.sentry.io/platforms/ruby/tracing/
---

# Set Up Tracing for Ruby

## Set up with Sentry CLI

Set up the Sentry Ruby SDK with the Sentry CLI. Install the CLI with one of these commands, then follow the Sentry CLI docs to finish setup.

**cURL**

```bash
curl https://cli.sentry.dev/install -fsS | bash
```

**PowerShell**

```powershell
irm https://cli.sentry.dev/install.ps1 | iex
```

**Homebrew**

```bash
brew install getsentry/tools/sentry
```

**npx**

```bash
npx sentry@latest
```

[Learn more about the Sentry CLI](https://cli.sentry.dev/)

With [tracing](https://docs.sentry.io/concepts/key-terms/tracing.md), Sentry follows requests, background jobs, and [agent runs](https://docs.sentry.io/product/agents.md) across services so you can see where they fail or slow down. Spans record each service and the operations inside it. Learn more in [Distributed Tracing](https://docs.sentry.io/concepts/key-terms/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.

Sentry can integrate with **OpenTelemetry**. You can find more information about it [here](https://docs.sentry.io/platforms/ruby/tracing/instrumentation/opentelemetry.md).

## [Configure](https://docs.sentry.io/platforms/ruby/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 `traces_sample_rate` option in your SDK config to a number between `0` and `1`. (For example, to send 20% of transactions, set `traces_sample_rate` 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 `traces_sampler` config option.

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

Tracing is available for our updated Ruby SDK (`sentry-ruby`, not `sentry-raven`).

```ruby
Sentry.init do |config|
  #...

  # Set a uniform sample rate between 0.0 and 1.0
  # We recommend adjusting the value in production:
  config.traces_sample_rate = 1.0

  # or control sampling dynamically
  config.traces_sampler = lambda do |sampling_context|
    # sampling_context[:transaction_context] contains the information about the transaction
    # sampling_context[:parent_sampled] contains the transaction's parent's sample decision
    true # return value can be a boolean or a float between 0.0 and 1.0
  end
end
```

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

## [Verify](https://docs.sentry.io/platforms/ruby/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/ruby/tracing/instrumentation/custom-instrumentation.md) content.

While you're testing, set `traces_sample_rate` 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 `traces_sample_rate` value, or switch to using `traces_sampler` to selectively sample and filter your transactions, based on contextual data.

## [Agent Tracing](https://docs.sentry.io/platforms/ruby/tracing.md#agent-tracing)

If you're building with agents or LLMs, the same trace can include the agent run, so you can see the model calls, tool executions, and where the run failed or slowed down. With tracing already enabled, you can use custom instrumentation to capture agent spans and connect them to the rest of your application traces.

[Set up Agent Tracing](https://docs.sentry.io/platforms/ruby/tracing/instrumentation/custom-instrumentation/ai-agents-module.md) to get started.

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

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

  Learn how to instrument tracing in your app using Sentry's Ruby SDK.

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

  Learn how to connect events across applications/services using the Sentry Ruby SDK.

## Pages in this section

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