Manage Your Attachments Quota
Sending all your error attachments to Sentry may consume your
Applying the proper filters, SDK configuration, and rate limits is an iterative and on-going process, but these tips will show you how to get the most out of your error events. These tips are ordered from easiest or least time-consuming to most challenging or potentially time-consuming. The first three options are all things you can do in sentry.io, whereas the remaining one is something you'll do in the SDK.
Before You Begin: Check Your Quota Usage
You can look at your attachments in aggregate in the "Usage Stats" tab of Stats. This information will help you answer key questions about the breakdown of your incoming attachments or which projects are consuming your
This page is accessible to all members of your organization, so Owners in your Sentry org can share this page with the developers directly responsible for a given project. Also, you can come back to this page to assess if the changes you've made are having the desired effect.
How can I see a breakdown of incoming attachments?
The Usage Stats tab displays details about the total amount of data Sentry has received across your entire organization for up to 90 days. The page breaks down the events (by project) into three categories: accepted, dropped, or filtered. Only accepted attachments affect your
What are my busiest projects?
The "Project" table in the "Usage Stats" tab of Stats breaks down your data by project, so you can see which ones are consuming your
1. Adjusting Quotas
Quotas can only be updated by a Billing or Owner member of your Sentry organization.
Once your attachments volume is approaching or has exceeded the
If this is your first time exceeding quota and you're on a paid plan, however, you'll be entered into a one-time grace period. Learn more about the grace period in this Help article.
If you're dropping attachments that you want to keep because you've exceeded your
When you exceed your quota threshold, the server will respond with a 429 HTTP status code, which communicates to SDKs and clients to stop sending events and thus their associated attachments. This status code comes with a
Retry-After header that indicates the time for which this rate limit is active. However, clients are not supposed to retry events, but instead drop events until the rate limit has expired, to prevent queue backlogs. Note, that since event ingestion and rate limiting happen asynchronously, the 429 HTTP status code is always slightly delayed.
To increase your quota, go to Settings > Subscription and click the "Manage Subscription" button to access your subscription options. When you increase your quota, the change goes into effect immediately.
If you're on a Developer plan and want to increase your quota, you'll need to upgrade to a Team or Business plan. On these plans you can prepay for more attachments volume and purchase on-demand volume, as needed. Learn about Sentry's plans on our pricing page.
If you upgrade from Team to Business mid-billing period, your on-demand pricing changes retroactively.
If the amount of data you need for attachments is steadily increasing, you may want to increase your reserved capacity or volume. Reserved volume is less expensive than on-demand volume since you prepay for it. It also allows you to choose the amount of data you want to have available for attachments beforehand rather than just setting an arbitrary on-demand budget. Learn more about reserved volume in our pricing documentation.
You shouldn't increase your reserved volume if you think your need for more events is temporary, since reducing your reserved volume is tied to your billing period.
If you need to increase your attachments
Plan downgrades and decreases in reserved volume are processed at the end of your billing period, and remaining volume cannot be refunded. For example, if you have a monthly billing period that starts on the 5th of the month, and you decrease your reserved volume on June 20th, then this change will be processed on July 4th. Your billing period beginning on July 5th will reflect your new reserved volume.
If you have an annual billing period, plan downgrades and decreases in reserved volume go into effect at the beginning of your next billing year.
Changes to on-demand volume typically go into effect immediately and are guaranteed to go into effect within 24 hours. However, you can't decrease your on-demand budget to less than what you've consumed in the current period.
To decrease your
We strongly recommend that you make subscription changes before the last day of your billing period. Depending on your time zone, in some cases, changes made on the last day of the billing period will not go into effect until the next billing period.
2. Rate Limiting
If you have enabled the storage of crash reports, you can set limits for the maximum number of crash reports that will be stored per issue. To set up these limits, go to Settings > Security & Privacy and make a selection in the "Store Native Crash Reports" dropdown. This setting applies to your entire organization.
3. Inbound Data Filters
SDK configuration requires changes to your source code and depends on your next deployment, but server-side filters can be easily configured per project in the "Data Filters" section of [Project] > Settings > Inbound Filters.
While you can't set filters for attachments directly, when you set inbound filters for error events, their associated attachments are indirectly filtered. Learn more about setting data filters for error events in Manage Your Error Quota.
4. 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:
- Events, attachments, and requests exceeding payload size limits are immediately dropped with a
413 Payload Too Largeerror. Sentry allows compressed content encoding, and applies separate limits before and after decompression.
- Fields exceeding the individual size limits are afterwards trimmed and truncated at a best effort.
To avoid using up your attachments
The precise limits may change over time. For more information, please refer to the following resources:
If the event exceeds 200KB compressed or 1MB decompressed for events and 20MB compressed or 100MB decompressed for minidump uploads (all files combined), the event will be rejected.
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").