Manage Your Transaction Quota

In most cases, sending all transaction events to Sentry could generate more performance data than you'd find useful and might use up your transactions

quotaThe monthly number of events that you pay Sentry to track.
too quickly. Sentry provides tools to control the type and amount of transactions that are monitored. This allows you to have transaction data that's actionable and meaningful, and to manage your quota.

Applying the proper SDK configuration is an iterative and on-going process, but these tips will show you how to best use Sentry's tools to get the most out of your transaction events. These tips are ordered from easiest or least time-consuming to most challenging or potentially time-consuming. The first two options are things you can do in sentry.io, whereas the remaining ones are things you'll do in the SDK.

Before You Begin: Check Your Quota Usage

You can look at your events in aggregate in the "Usage Stats" tab of Stats. This information will help you answer key questions about the breakdown of your incoming events or which projects are consuming your

quotaThe monthly number of events that you pay Sentry to track.
. The answers to these questions can help you figure out where you need to do further fine-tuning of your SDK filters and configuration.

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 check if the changes you've made are having the desired effect.

How can I see a breakdown of incoming events?

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 events affect your

quotaThe monthly number of events that you pay Sentry to track.
:

Usage Stats page showing transactions

What are my busiest projects?

The "Project" table in the "Usage Stats" tab of Stats breaks down your events by project so you can see which ones are consuming your

quotaThe monthly number of events that you pay Sentry to track.
. Clicking on the settings icon next to a project name in the table will open the project's settings, where you can manage its inbound filters.

Which transactions are consuming my quota?

You can set up a query in Discover to see which transactions you're receiving the most and if you want to adjust that. When you're building the query, search for event.type:transaction and then set the columns to title, project, and count, as shown below:

Busiest Projects

Once the changes are applied, sort the "Results" table by the "COUNT()" column to display your busiest transactions:

Busiest Issues

1. Adjusting Quotas

Once your event volume is approaching or has exceeded the

quotaThe monthly number of events that you pay Sentry to track.
, teammates with the "Owner" organization permission level will receive notification emails. You can then choose to increase or decrease your quota.

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.

Increasing Quotas

If you're dropping events that you want to keep because you've exceeded your

quotaThe monthly number of events that you pay Sentry to track.
, add to your quota at any time during your billing period by either increasing your reserved or on-demand quota.

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. 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 event volume and purchase on-demand volume, as needed. Learn about Sentry's plans on our pricing page.

Reserved Volume

If the number of events you need 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 number of events that you want to have available 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.

On-Demand Budget

If you need to increase your event

quotaThe monthly number of events that you pay Sentry to track.
temporarily, we recommend that you add or increase on-demand budget. This is ideal for situations like rolling out a new version of your application where you anticipate more events for the month. To add on-demand capacity or volume, you enter a monthly maximum budget on either a shared or per-category (errors, transactions, and attachments) basis. Learn more about on-demand volume in our pricing documentation.

Decreasing Quotas

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.

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

quotaThe monthly number of events that you pay Sentry to track.
, go to Settings > Subscription and click "Manage Subscriptions". When you reach the "Review & Confirm" step, the date that these changes go into effect will be displayed:

The Review & Confirm step of a subscription update.

2. Inbound Filters

While SDK configuration requires changes to your source code and depends on your next deployment, server-side filters can be easily configured per project in the "Data Filters" section of [Project] > Settings > Inbound Filters.

Once applied, you can track the filtered events (numbers and cause) using the graph provided at the top of the "Inbound Filters" page.

Built-in Inbound Filters

Sentry provides several methods to filter all events and attachments server-side, which are applied before checking for potential rate limits. Inbound filters include:

  • Common browser extension errors
  • Events coming from localhost
  • Known legacy browsers errors
  • Known web crawlers
  • Specific release versions of your code
  • Certain IP addresses

The first four options above are settings that you simply toggle on or off. Setting the others is explained further below.

After these checks are processed, events and attachments that aren't dropped based on these filters count toward your

quotaThe monthly number of events that you pay Sentry to track.
. They're accepted into Sentry, where they're persisted and stored.

IP Filters

If you have a rogue client, Sentry supports blocking an IP from sending data. Navigate to [Project] > Settings > Inbound Filters to add the IP addresses (or subnets) in the "IP Addresses" field.

Filter by Release

If you discover a problematic release causing excessive noise, Sentry supports ignoring all events and attachments from that release. Navigate to [Project] > Settings > Inbound Filters, then add the release to the "Releases" field.

3. 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. Setting a sample rate is documented for each SDK.

The SDK sample rate is not dynamic; changing it requires re-deployment. Also, keep in mind that setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project may better suit your needs.

4. SDK Configuration: Tracing Options

When you configure your the SDK, you can control the number of transactions that are sent to Sentry by setting the tracing options. You can also set up custom instrumentation for performance monitoring to capture certain types of transactions.

Help improve this content
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").