Set Up

With performance monitoring, 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.

Enable Tracing

The platform or SDK you've selected either does not support this functionality, or it is missing from documentation.

If you think this is an error, feel free to let us know on GitHub.

Configure the Sample Rate

Sampling for transactions must also be configured before tracing is be enabled in your app. Set the sample rate for your transactions by either:

  1. 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.)
  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.

Copied
#include <sentry.h>

sentry_options_t *options = sentry_options_new();

// The native SDK currently only supports uniform sample rates.
sentry_options_set_traces_sample_rate(options, 0.2);
...
sentry_init(options);

Learn more about how the options work in Sampling Transactions.

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 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, we recommend lowering this value in production by either lowering your traces_sample_rate value, or switching to using traces_sampler to dynamically sample and filter your transactions.

Next Steps:

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").