GinSet Up Profiling
Go Profiling is currently in alpha. Alpha features are still in progress and may have bugs. We recognize the irony.
With profiling, Sentry tracks your software's performance by sampling your program's call stack in a variety of environments. This feature collects function-level information about your code and enables you to fine-tune your program's performance. Sentry's profiler captures function calls and their exact locations, aggregates them, and shows you the most common code paths of your program. This highlights areas you could optimize to help increase both the performance of your code and increase user satisfaction, as well as drive down costs.
Go Profiling alpha is available since SDK version 0.22.0.
To enable profiling, set the ProfilesSampleRate:
err := sentry.Init(sentry.ClientOptions{
Dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",
EnableTracing: true,
TracesSampleRate: 1.0,
ProfilesSampleRate: 1.0,
})
The Profiles_sample_rate setting is relative to the Traces_sample_rate setting.
For Profiling to work, you have to first enable Sentry’s performance monitoring via traces_sample_rate (like in the example above). Read our performance setup documentation to learn how to configure sampling. If you set your sample rate to 1.0, all transactions will be captured.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").
