Data and quotas are interconnected in Sentry. At the most basic level, when you subscribe to Sentry, you pay for the amount of data — events (errors, replays, and transactions) and attachments — to be tracked. Each of these data categories has a
To see which of your projects are using up your quota, you can review the "Usage" tab of Stats. This page is accessible to all members of your organization, so a Billing or Owner member can share this page with the developers directly responsible for a given project. In addition, you can come back to this page to check if the changes you've made are having the desired effect:
You can also download a project breakdown report in the "Usage History" tab of Settings > Subscriptions (only accessible to Owner and Billing members of your Sentry organization).
Sentry's flexibility means you can exercise fine-grained control over which events and attachments count toward your quota. This page provides you with high-level information about strategies for managing your quota, but you can get more detailed information in:
- Manage Your Error Quota
- Manage Your Transaction Quota
- Manage Your Replay Quota
- Manage Your Attachments Quota
Manage Your Quota - Quick Guide
This list of strategies for managing your
|1. Check your spike protection is enabled||✓|
|2. Adjust your quota||✓||✓||✓|
|3. Rate limit your events or attachments||✓||✓|
|4. Review repeated events||✓|
|5. Filter your events||✓||✓||✓|
|6. Update your SDK sample rate||✓||✓|
|7. Apply SDK filtering||✓||✓|
|8. Update your SDK configuration||✓||✓|
|9. Manage data size||✓||✓||✓|
Let's clarify a few terms to start:
- Event - An event is one instance of you sending data to Sentry, excluding attachments. Generally, this data is an error or a transaction.
- Error - What counts as an error varies by platform, but in general, if there's something that looks like an exception, it can be captured as an error in Sentry. Sentry automatically captures errors, uncaught exceptions, and unhandled rejections, as well as other types of errors, depending on platform. A grouping of similar errors makes an issue.
- Transaction - A transaction represents a single instance of a service being called to support an operation you want to measure or track, like a page load. Transaction events are grouped by the transaction name.
- Replay - Session Replays are video-like reproductions of users’ sessions as they navigate your app or website.
- Attachment - Attachments are stored additional files, such as config files, log files, or stored mini-dumps, that are related to an error event. Unless the option to store crash reports is enabled, Sentry will use these files only to create an event, and then drop them.
- Data - Anything you send to Sentry. This includes events (errors or transactions), attachments, and event metadata.
- Quota - Your quotaThe monthly number of events that you pay Sentry to track.is the amount of data (errors, transactions, attachments) that you pay Sentry to track.
Manage Your Quota - Overview
Sentry completes a thorough evaluation of each event to determine if it counts toward your
Before completing any of these evaluations, Sentry confirms that each event includes a valid DSN and project as well as whether the event can be parsed. In addition, for error events, Sentry validates that the event contains valid
This list is ordered from easiest or least time-consuming to most challenging or potentially time-consuming. This isn't the order in which evaluations take place.
1. Spike Protection
Sentry’s spike protection prevents huge overages in error events from consuming your event volume, and it's enabled for all accounts by default. You can confirm that spike protection is enabled in Settings > Subscription. Learn more about how spike protection works and how to manage spikes in Manage Your Error Quota.
2. Adjusting Your Quota
Events and attachments that exceed your
3. Rate Limits
You can add limits for error events on a per-project basis in [Project] > Settings > Client Keys (DSN). If the event rate limit for a project has been exceeded, and your subscription allows, the event won't be counted. You can also rate limit attachments on an organization level in Settings > Security & Privacy. Learn more in Manage Your Error Quota and Manage Your Attachments Quota.
4. Event Repetition
In some cases, repeated events can count against your
5. Inbound Filters
If an inbound filter is applied for a type of error, transaction, or attachment, and your subscription allows, it won't be counted. You can manage these in [Project] > Settings > Inbound Filters. Learn more in Manage Your Error Quota, Manage Your Transaction Quota, Manage your Replay Quota, and Manage Your Attachments Quota.
6. SDK Sample Rate
If a sample rate is defined for the SDK, the SDK evaluates whether this event should be sent as a representative fraction of events, effectively limiting the number of errors and transactions you send to Sentry. Setting a sample rate is documented for each SDK, but you can also learn more in Manage Your Error Quota and Manage Your Transaction Quota.
7. SDK Filtering:
All Sentry SDKs support the
beforeSend callback method, which you can use to modify the data of an error event or to drop it completely. Many also support
beforeSendTransaction. Learn more in Manage Your Error Quota and Manage Your Transaction Quota.
8. SDK Configuration
The SDK configuration either allows an event to be sent to Sentry or filters it out. Configuration is documented for each SDK, but you can also learn more in Manage Your Error Quota and Manage Your Transaction Quota.
9. Size Limits
Sentry imposes limits on various fields within an event, as well as the size of full events and the requests they are sent in, which can affect your attachments
What Counts Toward Your Quota - Quick Guide
This table outlines whether or not an an event or attachment that you send to Sentry counts against your
|Scenario||Yes, this data counts|
|Spike protection activation threshold has been reached (errors)|
|Spike protection no longer active (errors)||✓|
|Your quota hasn't been reached||✓|
|Your quota has been exceeded|
|A rate limit for a project has been applied (errors, attachments)|
|This is a repeated event for which issues were previously set to Delete & Discard (errors)|
|This is a repeated event for a previously resolved issue (errors)||✓|
|This is a repeated event for an issue that you've set to Ignore||✓|
|The event defies inbound filters configured in sentry.io|
|The event is sent after the SDK sample rate has been exceeded|
|The event isn't sent based on SDK filters|
|The event isn't sent based on SDK configuration|
|Size limits have been exceeded|
|Issues are created from accepted error and transaction events|
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").