diff --git a/src/docs/product/accounts/early-adopter.mdx b/src/docs/product/accounts/early-adopter.mdx index 78cf487ff6a19..f59ff9af40180 100644 --- a/src/docs/product/accounts/early-adopter.mdx +++ b/src/docs/product/accounts/early-adopter.mdx @@ -19,6 +19,5 @@ Limitations: - [Issue Status](https://sentry-docs-git-update-beta-test-archiving.sentry.dev/product/issues/states-triage/) tags, including [Escalating Issues](https://sentry-docs-git-update-beta-test-archiving.sentry.dev/product/issues/states-triage/escalating-issues/) - [Priority Sort](/product/issues#issue-sort) algorithm improvements -- [Grouping Breakdown](/product/data-management-settings/event-grouping/grouping-breakdown/) - [Issue Reprocessing](/product/issues/reprocessing/) - [Span Summary](/product/performance/transaction-summary/#span-summary) diff --git a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_level_01.png b/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_level_01.png deleted file mode 100644 index d9b2ef605e1a5..0000000000000 Binary files a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_level_01.png and /dev/null differ diff --git a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_level_02.png b/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_level_02.png deleted file mode 100644 index bb6f244ee5259..0000000000000 Binary files a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_level_02.png and /dev/null differ diff --git a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_level_03.png b/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_level_03.png deleted file mode 100644 index ea9aeb1faafa6..0000000000000 Binary files a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_level_03.png and /dev/null differ diff --git a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_01.png b/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_01.png deleted file mode 100644 index 4978b676a6171..0000000000000 Binary files a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_01.png and /dev/null differ diff --git a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_02.png b/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_02.png deleted file mode 100644 index 87ee288d1ccec..0000000000000 Binary files a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_02.png and /dev/null differ diff --git a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_03.png b/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_03.png deleted file mode 100644 index 3fd662b4387fb..0000000000000 Binary files a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_03.png and /dev/null differ diff --git a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/index.mdx b/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/index.mdx deleted file mode 100644 index 81f5645eb0aaa..0000000000000 --- a/src/docs/product/data-management-settings/event-grouping/grouping-breakdown/index.mdx +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: "Grouping Breakdown" -sidebar_order: 40 -description: "Learn more about the grouping algorithm and using the Grouping tab in Issue Details." ---- - - - This feature will be deprecated on March 8th, 2023. All projects using the - grouping breakdown will automatically transition to the latest grouping - strategy. No action is required on your part. After the transition, the - “grouping” tab in the UI will no longer appear. - - - - - - -Sentry's current grouping algorithm puts two error events into the same issue if they have the same stack trace. This approach sometimes creates multiple distinct issues for errors with the same root cause. - -If two distinct issues are created occasionally, you may be able to reduce the noise by manually [merging](/product/data-management-settings/event-grouping/merging-issues/) those issues. Alternatively, if you want coarser issue groups (thus fewer issues) by default, follow the process outlined here. - -## Enable the Grouping Breakdown (beta) - -Enable our newest grouping algorithm, which creates coarser (that is, fewer) issues by considering only the most relevant part of the stack trace. - -1. Join our Early Adopter program by navigating to **Settings > General Settings**. - -2. [Upgrade to the latest grouping algorithm](/product/data-management-settings/event-grouping#grouping-algorithms). - - - -Upgrading the grouping algorithm cannot be undone. - - - -## Use the Updated Grouping Breakdown - -After enabling the updated grouping algorithm, the grouping breakdown allows you to navigate subgroups of an issue to see what events would group together if a larger part of the stack trace were to be considered. You can do this in the "Grouping" tab of an issue. - -For example, if you have a crashing function called from multiple locations in your code ("intermediate function" "1" and "2"), when you move the slider all the way to the left, only the crashing frame is considered for grouping, and -all events are sorted into the same issue regardless of the calling location: - -![Breakdown of this issue on the highest level](breakdown_level_01.png) - -When you move the slider to the right, you can see what groups would be created -if the calling frame were also to be considered: - -![Breakdown of this issue on an intermediate level](breakdown_level_02.png) - -You can add another level by moving the slider all the way to the right. However, this does not add any new subgroups, as both calling functions are themselves called from the same location (`main`): - -![Breakdown of this issue on the deepest level](breakdown_level_03.png) - -## Sentinel & Prefix Frames - -With Grouping Breakdown enabled, Sentry groups events by identifying the most -interesting group of frames it can find in a stack trace. - -To mark frames as interesting, use the `+sentinel` and `+prefix` actions in [Stack Trace Rules](/product/data-management-settings/event-grouping/stack-trace-rules). For the first level, our algorithm looks for the first frame `X` which is marked as sentinel. The fingerprint of this frame is added to the level. If `X` is also a prefix frame, the next frame `Y` is also added. If `Y` is again a prefix frame, the next frame `Z` is added, and so on. - -If no sentinel frame is found, every frame that contributes to grouping according to the usual -stack trace rules (for example, `+group`) constitutes its own level of detail. - -#### Example - -Consider a stack trace with functions `a`, `b`, `c`, `d`, `e`, `f`, `g`, `h`, with `a` being the crashing frame -and `h` being the thread base. Imagine you have the following stack trace rules defined: - -```discover {tabTitle:Sentinel & Prefix Rules} -function:b +sentinel +prefix -function:c +prefix -function:f +sentinel -``` - -In this case - -- `b` is used for grouping because it is the first sentinel frame, -- `c` is used for grouping because `b` is a prefix frame, -- `d` is used for grouping because `c` is a prefix frame. - -This becomes visible in the [Breakdown tab](/product/data-management-settings/event-grouping/grouping-breakdown): - -![Example Breakdown with Sentinel & Prefix Frames (level 1)](breakdown_sentinels_level_01.png) - -Increasing the level adds the second sentinel: - -![Example Breakdown with Sentinel & Prefix Frames (level 2)](breakdown_sentinels_level_02.png) - -Finally, the deepest level contains the entire stack trace, ignoring sentinel and prefix frames: - -![Example Breakdown with Sentinel & Prefix Frames (level 3)](breakdown_sentinels_level_03.png) diff --git a/src/docs/product/data-management-settings/event-grouping/index.mdx b/src/docs/product/data-management-settings/event-grouping/index.mdx index 746d6a58f5cef..695a5805f6b68 100644 --- a/src/docs/product/data-management-settings/event-grouping/index.mdx +++ b/src/docs/product/data-management-settings/event-grouping/index.mdx @@ -60,8 +60,6 @@ This grouping usually works well, but two specific situations can throw it off: 1. Minimized JavaScript source code will destroy the grouping in detrimental ways. To avoid this, ensure that Sentry can access your [Source Maps](/platforms/javascript/sourcemaps/). 2. Modifying your stack trace by introducing a new level through decorators changes your stack trace, so the grouping will also change. To handle this, many SDKs support hiding irrelevant stack trace frames. For example, the Python SDK will skip all stack frames with a local variable called `__traceback_hide__` set to _True_. -You can also see what events would group together if a larger or smaller amount of stack trace frames were taken into account using the updated [Grouping Breakdown](/product/data-management-settings/event-grouping/grouping-breakdown/) (Early Adopters only). - ### Grouping By Exception If the stack trace is not available, but exception information is, then the grouping will consider the `type` and `value` of the exception if both pieces of data are present on the event. This grouping is a lot less reliable because of changing error messages. diff --git a/src/docs/product/data-management-settings/event-grouping/stack-trace-rules.mdx b/src/docs/product/data-management-settings/event-grouping/stack-trace-rules.mdx index a3efc10e8684e..ac8d3e9c3628f 100644 --- a/src/docs/product/data-management-settings/event-grouping/stack-trace-rules.mdx +++ b/src/docs/product/data-management-settings/event-grouping/stack-trace-rules.mdx @@ -114,7 +114,7 @@ category:telemetry -group #### Built-in Categories -Frame categorization is heavily used by our newest grouping algorithm, so [if you have it enabled](/product/data-management-settings/event-grouping/grouping-breakdown#enable-the-grouping-breakdown-beta), you can match on a variety of categories, including: +Frame categorization is heavily used by our newest grouping algorithm. You can match on a variety of categories, including: - `system` - detected system libraries - `std` - detected standard libraries