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.

Configure the Sample Rate

Once you configure the sample rate, tracing will 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 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.)
  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.

Performance Monitoring is available for the Sentry's Go SDK version ≥ 0.9.0.

Copied
func main() {
	err := sentry.Init(sentry.ClientOptions{
		// Specify a fixed sample rate:
        TracesSampleRate: 0.2,
        // Or provide a custom sampler:
		TracesSampler: sentry.TracesSamplerFunc(func(ctx sentry.SamplingContext) sentry.Sampled {
			return sentry.SampledTrue
		}),
	})
}

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.

Verify that performance monitoring is working correctly by setting TracesSampleRate 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 TracesSampleRate value, or switching to using TracesSampler to dynamically sample and filter your transactions.

Connecting Services

If you are also using Performance Monitoring for JavaScript depending on where your request originates there are two methods to connect your traces:

  1. For requests that start in your backend, this is done by adding a meta tag in your HTML template that contains tracing information.
  2. For requests that start in JavaScript, this is done by the SDK setting a header on requests to your backend.

Otherwise backend services with Performance Monitoring will connect automatically.

Next Steps:

You can edit this page on GitHub.