diff --git a/docs/organization/dynamic-sampling/img/investigation-bias-discover.png b/docs/organization/dynamic-sampling/img/investigation-bias-discover.png deleted file mode 100644 index a6e17c8d8cd5a..0000000000000 Binary files a/docs/organization/dynamic-sampling/img/investigation-bias-discover.png and /dev/null differ diff --git a/docs/organization/dynamic-sampling/img/investigation-bias-rule-created.png b/docs/organization/dynamic-sampling/img/investigation-bias-rule-created.png deleted file mode 100644 index 4b80a4e44f135..0000000000000 Binary files a/docs/organization/dynamic-sampling/img/investigation-bias-rule-created.png and /dev/null differ diff --git a/docs/organization/dynamic-sampling/img/investigation-bias-tx-summary.png b/docs/organization/dynamic-sampling/img/investigation-bias-tx-summary.png deleted file mode 100644 index ed5710ce3137a..0000000000000 Binary files a/docs/organization/dynamic-sampling/img/investigation-bias-tx-summary.png and /dev/null differ diff --git a/docs/organization/dynamic-sampling/index.mdx b/docs/organization/dynamic-sampling/index.mdx index 6dadb41c8921e..445d6d0f466b1 100644 --- a/docs/organization/dynamic-sampling/index.mdx +++ b/docs/organization/dynamic-sampling/index.mdx @@ -204,36 +204,3 @@ We deprioritize health check type transactions because while they're important f - `*/readyz` - `*/ping` -### Get Samples - - -The "Get Samples" button and the investigation rules that go along with it will be retired in Spring 2026. From that point on, you will no longer be able to create new investigation rules. - - -Our automated dynamic sampling priorities work well in a generic manner to collect a baseline of samples because they prioritize retaining data that's valuable for any customer at any given time. However, there are certain scenarios, such as investigating a particular issue, when very specific data becomes temporarily more important. In such cases, the automated sampling priorities may not provide enough samples, so you may want to create investigation rules. - -Investigation rules are sampling rules that can be created through the Sentry UI to temporarily boost the number of events collected for a particular scenario (for example, events with specific tag values). These rules can be created to retain more samples when too few (less than 5) are available. Once created, a rule will be active for up to 48 hours or until 100 samples are collected. You'll be notified via email when enough events have been collected. - -Investigation sampling rules only apply to transactions and don't guarantee that full traces will be sampled. The maximum number of sampling rules that can exist at the same time is 50. - -#### Creating a New Rule - -When you query transactions either in [Discover](/product/explore/discover-queries/) or in [Transaction Summary](/product/performance/transaction-summary/) and receive fewer than 5 samples, you can click "Get Samples" to create a new investigation rule and retain more samples of transactions for the respective query. - -![Investigation Mode in Discover](./img/investigation-bias-discover.png) - - - -This feature only applies to transactions. Therefore, in Discover, you have to specify `event.type:transaction` in the query to access the feature, whereas in Performance the event type is implicit. - - - -Clicking this button creates an investigation rule for the query. Once the rule is successfully created, a notification appears, and the button is replaced with a message showing the investigation is in progress and the amount of time it's been active. - -![Rule successfully created](./img/investigation-bias-rule-created.png) - -If a user performs the same search later and the investigation is still active, the notification will indicate that there's an active rule already collecting data for the query. - -It's also possible to create a rule from the Transaction Summary page in Performance. - -![Investigation Mode in Transaction Summary](./img/investigation-bias-tx-summary.png)