Issue
I'm having trouble understanding how my profiles are billed.
Applies To
- All SaaS Customers
- Profiling
Resolution
How your profiles will be billed depends on the SDK of your choice and whether you are using an up-to-date or a legacy Sentry plan:
- You can always refer to this page for which SDKs support which type of Profiling
- The up-to-date Sentry plans have reserved Spans
- The legacy Sentry plans have reserved Performance Units
Right now, Node.js and Python will send Continuous Profiles, while Android, iOS and macOS will send UI profiles. These profiles will consume your Pay-As-You-Go(PAYG)/On-Demand budget based on this pricing on both up-to-date and legacy Sentry plans.
Browser Javascript, React Native, Flutter, .NET, PHP, Ruby use Transaction-based Profiling, which means that each profile needs to be attached to a transaction. Therefore, you will also have to enable tracing, and ensure that you are sending transactions/spans to Sentry.
If you have a legacy Sentry plan and are using Transaction-based Profiling, every transaction with a profile attached to it will consume 1.3 Performance Units.
If you have an up-to-date Sentry plan, your Transaction-Based Profiles will be converted into UI Profiles, and be billed from your PAYG as mentioned above.