Skip to content

Commit

Permalink
Update span units to spans (#10536)
Browse files Browse the repository at this point in the history
* add index docs

* few more tweaks

* one more small change
  • Loading branch information
lizokm authored Jun 27, 2024
1 parent 6642ff0 commit d5ff7d5
Show file tree
Hide file tree
Showing 4 changed files with 23 additions and 24 deletions.
8 changes: 4 additions & 4 deletions docs/pricing/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ This page gives you an in-depth understanding of our pricing and billing structu

We bill based on the amount of data processed. Each [paid plan](https://sentry.io/pricing/) comes with the below pre-set monthly event volume, which is included in the price:
- 50k errors
- 10M span units
- 10M spans
- 50 replays
- 1 cron monitor
- 1GB of attachments
Expand Down Expand Up @@ -57,9 +57,9 @@ Please note that all per-category prices listed below have been rounded to the n

#### Tracing Pricing

Tracing is enabled by spans and will be billed for in span units.
Tracing is enabled by and will be billed for in spans.

| Span Unit Volume | Team Reserved | Team PAYG | Business Reserved | Business PAYG |
| Span Volume | Team Reserved | Team PAYG | Business Reserved | Business PAYG |
| ---------------- | ------------ | ---------- | ---------------- | -------------- |
| >10M-100M | $0.0000016 | $0.0000020 | $0.0000032 | $0.0000040 |
| >100M | $0.0000014 | $0.0000018 | $0.0000029 | $0.0000036 |
Expand Down Expand Up @@ -110,7 +110,7 @@ For more information on how to manage your monthly spending, check out our [Quot
Sentry uses two different billing cycles: one for your paid plan and reserved volume, and another one for your pay-as-you-go usage.

- **Subscription billing cycle:** Billing cycle for your paid plan and reserved volume for which you can elect to be billed on either a monthly or an annual basis.
- **Pay-as-you-go billing cycle:** Billing cycle for your pay-as-you-go usage, for which you'll be billed on a monthly basis.
- **Pay-as-you-go billing cycle:** Billing cycle for your pay-as-you-go usage, for which you'll be billed on a monthly basis.

_If you're on a monthly subscription billing cycle, your pay-as-you-go billing cycle will be aligned to it._

Expand Down
19 changes: 9 additions & 10 deletions docs/pricing/quotas/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -22,13 +22,13 @@ Sentry's flexibility means you can exercise fine-grained control over which even

## How to Manage Your Quota

There are a number of things you can do to manage your quota, as shown in the table below. Actions are listed in order from easiest and fastest, to most challenging and potentially time-consuming. The checkmarks tell you whether the action helps you manage errors, span units, replays, attachments, or some combination of the four.
There are a number of things you can do to manage your quota, as shown in the table below. Actions are listed in order from easiest and fastest, to most challenging and potentially time-consuming. The checkmarks tell you whether the action helps you manage errors, spans, replays, attachments, or some combination of the four.

The first 6 actions in the list can all be done in [sentry.io](https://sentry.io), while the rest have to be done in an SDK.

{/*<!-- prettier-ignore-start -->*/}

| Action | Errors | Span Units | Replays |Attachments |
| Action | Errors | Spans | Replays |Attachments |
| ------ | ------ | ------------ | ----------- |----------- |
| [Ensure spike protection is enabled](#spike-protection) | &check; | &check; | | &check; |
| [Adjust your quota](#adjusting-your-quota) | &check; | &check; | &check; | &check; |
Expand Down Expand Up @@ -62,7 +62,7 @@ Spike Protection can be enabled on a per-project basis for your organization by

### Adjusting Your Quota

Events and attachments that exceed your quota will not be accepted, so you may want to increase your quota. Conversely, you might want to decrease your quota or adjust your reserved and pay-as-you-go quotas to better control your spending. Learn about adjusting your quota in [Manage Your Error Quota](/pricing/quotas/manage-event-stream-guide/adjusting-quotas), [Manage Your Span Units Quota](/pricing/quotas/manage-transaction-quota/), [Manage your Replay Quota](/pricing/quotas/manage-replay-quota/), and [Manage Your Attachments Quota](/pricing/quotas/manage-attachments-quota/#adjusting-quotas).
Events and attachments that exceed your quota will not be accepted, so you may want to increase your quota. Conversely, you might want to decrease your quota or adjust your reserved and pay-as-you-go quotas to better control your spending. Learn about adjusting your quota in [Manage Your Error Quota](/pricing/quotas/manage-event-stream-guide/adjusting-quotas), [Manage Your Span Quota](/pricing/quotas/manage-transaction-quota/), [Manage your Replay Quota](/pricing/quotas/manage-replay-quota/), and [Manage Your Attachments Quota](/pricing/quotas/manage-attachments-quota/#adjusting-quotas).

### Rate Limits

Expand All @@ -74,19 +74,19 @@ In some cases, repeated events can count against your quota, so it's important t

### Inbound Filters

If an inbound filter is applied for a type of error, transaction/span, 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](/pricing/quotas/manage-event-stream-guide/#inbound-data-filters), [Manage Your Span Units Quota](/pricing/quotas/manage-transaction-quota/#inbound-filters), [Manage your Replay Quota](/pricing/quotas/manage-replay-quota/), and [Manage Your Attachments Quota](/pricing/quotas/manage-attachments-quota/#inbound-data-filters).
If an inbound filter is applied for a type of error, transaction/span, 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](/pricing/quotas/manage-event-stream-guide/#inbound-data-filters), [Manage Your Span Quota](/pricing/quotas/manage-transaction-quota/#inbound-filters), [Manage your Replay Quota](/pricing/quotas/manage-replay-quota/), and [Manage Your Attachments Quota](/pricing/quotas/manage-attachments-quota/#inbound-data-filters).

### 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/spans you send to Sentry. Setting a sample rate is documented [for each SDK](/platform-redirect/?next=/configuration/sampling/), but you can also learn more in [Manage Your Error Quota](/pricing/quotas/manage-event-stream-guide/#sdk-sample-rate) and [Manage Your Span Units Quota](/pricing/quotas/manage-transaction-quota/#sdk-configuration-tracing-options/).
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/spans you send to Sentry. Setting a sample rate is documented [for each SDK](/platform-redirect/?next=/configuration/sampling/), but you can also learn more in [Manage Your Error Quota](/pricing/quotas/manage-event-stream-guide/#sdk-sample-rate) and [Manage Your Span Quota](/pricing/quotas/manage-transaction-quota/#sdk-configuration-tracing-options/).

### SDK Filtering: `beforeSend` and `beforeSendTransaction`

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](/pricing/quotas/manage-event-stream-guide/#sdk-filtering-beforesend) and [Manage Your Span Units Quota](/pricing/quotas/manage-transaction-quota/#sdk-filtering-beforesendtransaction).
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](/pricing/quotas/manage-event-stream-guide/#sdk-filtering-beforesend) and [Manage Your Span Quota](/pricing/quotas/manage-transaction-quota/#sdk-filtering-beforesendtransaction).

### SDK Configuration

The SDK configuration either allows an event to be sent to Sentry or filters it out. Configuration is documented [for each SDK](/platform-redirect/?next=/configuration/filtering/), but you can also learn more in [Manage Your Error Quota](/pricing/quotas/manage-event-stream-guide/#sdk-configuration) and [Manage Your Span Units Quota](/pricing/quotas/manage-transaction-quota/#sdk-configuration-tracing-options).
The SDK configuration either allows an event to be sent to Sentry or filters it out. Configuration is documented [for each SDK](/platform-redirect/?next=/configuration/filtering/), but you can also learn more in [Manage Your Error Quota](/pricing/quotas/manage-event-stream-guide/#sdk-configuration) and [Manage Your Span Quota](/pricing/quotas/manage-transaction-quota/#sdk-configuration-tracing-options).

### Size Limits

Expand Down Expand Up @@ -128,7 +128,6 @@ Let's clarify a few terms:
- **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](/product/issues/).
- **Event** - An event is one instance of you sending data to Sentry, excluding attachments. Generally, this data is an error or a transaction/span.
- **Replay** - Session Replays are video-like reproductions of users' sessions as they navigate your app or website.
- **Span** - The basic unit that [traces](/concepts/key-terms/tracing/distributed-tracing/) are composed of. Multiple spans make up a trace in Sentry and share a trace_id.
- **Span Unit** - A billing unit in Sentry that maps to span usage.
- **Span** - A billing unit in Sentry that maps to span usage. Also the basic unit that [traces](/concepts/key-terms/tracing/distributed-tracing/) are composed of. Multiple spans make up a trace in Sentry and share a trace_id.
- **Profile** - A snapshot of your code's resource usage obtained by periodically capturing the call stack as your application runs.
- **Quota** - Your quota is the amount of data (errors, span units, replays, attachments) that you pay Sentry to track.
- **Quota** - Your quota is the amount of data (errors, spans, replays, attachments) that you pay Sentry to track.
14 changes: 7 additions & 7 deletions docs/pricing/quotas/manage-transaction-quota.mdx
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
---
title: Manage Your Span Units Quota
title: Manage Your Span Quota
keywords: ["best practices"]
sidebar_order: 40
description: "Learn how to use the tools Sentry provides to control your span unit quota."
description: "Learn how to use the tools Sentry provides to control your span quota."
---
In most cases, sending all span events to Sentry could generate more data than you'd find useful and might use up your span units too quickly. Sentry provides tools to control the _type_ and _amount_ of spans that are monitored. This allows you to have tracing data that's actionable and meaningful.
In most cases, sending all span events to Sentry could generate more data than you'd find useful and might use up your spans too quickly. Sentry provides tools to control the _type_ and _amount_ of spans that are monitored. This allows you to have tracing data that's actionable and meaningful.

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 span units. 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](https://sentry.io), whereas the remaining ones are things you'll do in the SDK.
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 spans. 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](https://sentry.io), whereas the remaining ones are things you'll do in the SDK.

## Before You Begin: Check Your Quota Usage

Expand Down Expand Up @@ -53,7 +53,7 @@ When you exceed your quota threshold, the server will respond with a 429 HTTP st

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 span units and purchase pay-as-you-go budget, as needed. Learn about Sentry's plans on our [pricing page](https://sentry.io/pricing/).
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 spans and purchase pay-as-you-go budget, as needed. Learn about Sentry's plans on our [pricing page](https://sentry.io/pricing/).

<Alert>

Expand All @@ -63,13 +63,13 @@ If you upgrade from Team to Business mid-billing period, your pay-as-you-go pric

### 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 pay-as-you-go volume since you prepay for it. It also allows you to choose the number of span units that you want to have available beforehand. Learn more about [reserved volume](/pricing/#prepaid-reserved-capacity) in our pricing documentation.
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 pay-as-you-go volume since you prepay for it. It also allows you to choose the number of spans that you want to have available beforehand. Learn more about [reserved volume](/pricing/#prepaid-reserved-capacity) 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](#decreasing-quotas).

### Pay-as-you-go Budget

If you need to increase your span units quota temporarily, we recommend that you add or increase pay-as-you-go budget. This is ideal for situations like rolling out a new version of your application where you anticipate more events for the month. Learn more about [pay-as-you-go](/pricing/#pricing-how-it-works) in our pricing documentation.
If you need to increase your span quota temporarily, we recommend that you add or increase pay-as-you-go budget. This is ideal for situations like rolling out a new version of your application where you anticipate more events for the month. Learn more about [pay-as-you-go](/pricing/#pricing-how-it-works) in our pricing documentation.

### Decreasing Quotas

Expand Down
6 changes: 3 additions & 3 deletions docs/pricing/quotas/spend-allocation.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ This feature is only available to organizations with an Enterprise plan.

</Note>

Spend Allocation gives you the ability to prioritize your most important projects (or make sure that smaller projects don't get ignored). You can do this by setting aside a set amount of reserved volume (errors, span units, and attachments) to be used by those projects each month. This ensures that all the projects that are important to you are always monitored, regardless of the volume other projects consume.
Spend Allocation gives you the ability to prioritize your most important projects (or make sure that smaller projects don't get ignored). You can do this by setting aside a set amount of reserved volume (errors, spans, and attachments) to be used by those projects each month. This ensures that all the projects that are important to you are always monitored, regardless of the volume other projects consume.

<Note>

Expand All @@ -23,7 +23,7 @@ The per-project allocation you set is the **minimum** not the **maximum** number

To get started with Spend Allocation, look at your total reserved volume and decide how much of it you'd like to allocate to the projects you want monitored. For example, if your total reserved volume is 1M events, and you have two important projects, you can decide to allocate 300K events to project 1, 250k events to project 2, and leave the remaining unallocated pool of 450k events for all other projects.

For each project, you'll need to specify how much of your allocation goes to errors, to span units, and to attachments.
For each project, you'll need to specify how much of your allocation goes to errors, spans, and attachments.

<Note>

Expand All @@ -45,7 +45,7 @@ To enable spend allocation for your Org, you have to have **Manager, Billing, or

![Empty spend allocation page](./img/spend-allocation-empty.png)

2. Select the project, the event category (errors, span units, or attachments), and the allocation amount you'd like to set aside for that project. You can choose your allocations by volume or spend. Repeat the process for each event type you'd like to allocate to.
2. Select the project, the event category (errors, spans, or attachments), and the allocation amount you'd like to set aside for that project. You can choose your allocations by volume or spend. Repeat the process for each event type you'd like to allocate to.

![Create spend allocation modal](./img/spend-allocation-creation.png)

Expand Down

0 comments on commit d5ff7d5

Please sign in to comment.