Skip to main content

How do I disable profiling?

Issue

I want to disable profiling so that profile events stop consuming my Pay-As-You-Go (PAYG) budget. I need to know which SDK options to remove and how to confirm my projects are no longer sending profiles.

Applies To

  • All SaaS Customers

  • Profiling / Quota

Resolution

To stop profile events, make sure your SDK is not sampling profiles. Sentry has two profiling types, so remove the options for whichever you use (the option names below are for the Python SDK; other SDKs use the same names in their own casing, for example profileSessionSampleRate in JavaScript):

  • Transaction-based profiling (legacy): remove profiles_sample_rate and profiles_sampler.

  • Continuous or UI Profiling: remove profile_session_sample_rate and profile_lifecycle. If you use the manual lifecycle, also remove any start_profile_session and stop_profile_session (or start_profiler/stop_profiler) calls.

profile_session_sample_rate defaults to 0.0, so removing or omitting these options disables profiling. For details and option mappings, see the Continuous & UI Profiling migration guide and your SDK's profiling documentation.

To confirm which projects are still sending profiles:

  1. Go to Settings > Stats & Usage and open the Usage tab.

  2. In the Category dropdown, select each profiling category and set the date range to the last 90 days. The profiling categories are Profiles (legacy), Continuous Profile Hours, and UI Profile Hours.

    [Screenshot: the Settings > Stats & Usage page with the Category dropdown open, showing the profiling categories "Profiles (legacy)", "Continuous Profile Hours" (selected), and "UI Profile Hours", filtered to a 90-day range with a total of 0.29 Continuous Profile Hours.]

  3. If there are results, scroll to the project list to see which projects are sending profiles.

    [Screenshot: the project list on the Stats & Usage page, with the project name redacted, showing 0.29 total and 0.29 accepted profile hours, indicating the project is sending profiles.]

  4. Remove the profiling options above from those projects' SDK configuration.

Did this answer your question?