This feature is in beta and is only available if your organization is participating in its limited release. Features in beta are still in-progress and may have bugs. We recognize the irony. If you’re interested in participating, join the waitlist.
When you're using sentry.io, the transaction information that you see is generated by one of two types of events:
- Processed events - All the events that you send to Sentry, based on your SDK sample rate. Underlies metric-backed data.
- Indexed events - A sub-set of your processed events, based on your dynamic sampling settings. Underlies events-based data.
Processed events can include all the events that occur in your application or a sub-set of those. The number of these events that you send to Sentry is based on the sample rate that you set in the SDK. These events represent aggregate data. This is used in areas of the application like Performance and Dashboards. The larger your set of processed events, the better able we are to provide you with statistically significant insights into the performance of your application. In sentry.io, you may see the data generated from these events referred to as metrics or metric-backed.
Because these events represent aggregate data, Sentry doesn't store the full transaction data. So when you're viewing information in sentry.io that's based on these events, or based on metrics data, you can't drill down into the specifics of these events.
Indexed events are a sub-set of your processed events, and this sub-set is created based on your dynamic sampling settings. These are the events that you decide to keep from your processed events that Sentry stores for you. For these events, we store the complete transaction data, so you can drill down into each event for further insights. In sentry.io, you may see the data generated from these events referred to as transaction data or events-based.
7.0.0 or higher).