Set Up Performance
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.
If you’re adopting Performance in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
Configure the Sample Rate
Sampling for transactions must also be configured before
- Setting a uniform sample rate for all transactions using the
traces_sample_rateoption in your SDK config to a number between
1. (For example, to send 20% of transactions, set
- Controlling the sample rate based on the transaction itself and the context in which it's captured, by providing a function to the
The two options are meant to be mutually exclusive. If you set both,
traces_sampler will take precedence.
Performance Monitoring is available for our updated Ruby SDK (
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 how the options work in Sampling Transactions.
While you're testing, set
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.
- For requests that start in your backend, by adding a meta tag in your HTML template that contains tracingThe process of logging the events that took place during a request, often across multiple services.information.
Otherwise, backend services with Performance Monitoring connect automatically.
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").