-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Add new profiling spend management page WIP #11762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,92 @@ | ||
| --- | ||
| title: Manage Your Profiling Quota | ||
| keywords: ["best practices"] | ||
| sidebar_order: 45 | ||
| description: "Learn how to control the number of profiles that you send and pay for." | ||
| --- | ||
|
|
||
| Sentry's [profiling](/product/explore/profiling/) feature provides precise, code-level visibility into application execution in a production environment. Profiling lets you see your call stack in detail without you needing to add any custom instrumentation. With Profiling, you can quickly identify hot paths in your code and understand potential performance bottlenecks. | ||
|
|
||
| Sentry offers [two profiling modes](/product/explore/profiling/transaction-vs-continuous-profiling/): transaction-based and continuous, which have different billing implications. For continuous profiling, cost is determined by the length of the profile in milliseconds and is billed in hours. | ||
|
|
||
|
|
||
|
|
||
| <Note> | ||
|
|
||
| The PAYG budget is only available on **paid plans**. | ||
|
|
||
| </Note> | ||
|
|
||
| ## Managing Usage | ||
|
|
||
|
|
||
|
|
||
| ## Key Terms | ||
|
|
||
| - **Reserved Quota**: The number of cron monitors included in your plan. | ||
| - **Pay-As-You-Go (PAYG) Budget**: A budget you set to pay for additional monitors beyond your reserved quota. | ||
| - **Reusable Quota**: Quota freed up by deactivating or deleting monitors within the same billing period, which can be reused for new or reactivated monitors at no additional cost. | ||
|
|
||
| ## Viewing and Adjusting Your PAYG Budget | ||
|
|
||
| To check or adjust your monthly PAYG budget for profiling: | ||
|
|
||
| 1. Go to **Organization Settings > Subscription**. | ||
| 2. Review your current PAYG budget. | ||
| 3. Adjust your budget as needed. | ||
|
|
||
| **Activation Process:** | ||
|
|
||
| 1. **Check for Reusable Quota** | ||
|
|
||
| - Sentry first checks if there's any **reusable quota** from monitors deactivated or deleted within the **same billing period**. | ||
| - If available, the monitor is activated using this quota **at no additional cost**. | ||
|
|
||
| 2. **Use PAYG Budget or Reserved Quota** | ||
|
|
||
| - If no reusable quota is available, Sentry uses your **reserved quota** or **PAYG budget** to activate the monitor. | ||
| - The cost is deducted from your PAYG budget. | ||
|
|
||
| <Alert> | ||
|
|
||
| **Important:** Quota reuse only applies **within the same billing period** and to monitors that were previously assigned and billed. | ||
|
|
||
| </Alert> | ||
|
|
||
| ### Activation Across Billing Periods | ||
|
|
||
| At the start of each new billing period: | ||
|
|
||
| - **Quota Reset**: All quotas reset, and any reusable quota from the previous period is no longer available. | ||
| - **Re-evaluation of Monitors**: | ||
|
|
||
| - If you have sufficient **reserved quota** or **PAYG budget**, monitors that were previously active will remain active. | ||
| - If there isn't enough budget, monitors may be automatically deactivated. | ||
| - **Manual Deactivations or Deletions**: Monitors that were manually deactivated or deleted will remain in that state. | ||
|
|
||
| ## Deactivating or Deleting Monitors | ||
|
|
||
| You can manually deactivate or delete monitors at any time from the **Crons** page. | ||
|
|
||
| **Effects of Deactivation or Deletion:** | ||
|
|
||
| - **Quota Becomes Reusable**: The quota from the deactivated or deleted monitor becomes available for reuse **within the same billing period**. | ||
| - **Billing Impact**: Deactivated or deleted monitors will **count** towards your billing quota if they were previously active in the current billing period. Otherwise, they don't count towards your billing quota. | ||
|
|
||
| <Note> | ||
|
|
||
| - **Quota Reuse Limitations**: | ||
|
|
||
| - Reusable quota is only available **within the same billing period**. | ||
| - Applies only to monitors that were previously active and billed. | ||
| - **Reusable quota does not carry over to new billing periods.** | ||
|
|
||
| </Note> | ||
|
|
||
| ## Tips for Managing Your Profiles | ||
|
|
||
| - **Monitor Your Usage**: Regularly check your active monitors and PAYG budget to avoid unexpected deactivations. | ||
| - **Adjust Budget as Needed**: If you plan to add more monitors, consider increasing your PAYG budget beforehand. | ||
| - **Plan for Renewal**: Remember that quotas reset each billing period. Ensure you have sufficient budget to keep monitors active. | ||
|
|
||
| By understanding how monitor activation and billing work, you can effectively manage your cron monitors and avoid interruptions in your monitoring. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.