From d54594d0abd33cb87de7b9ce8536f53d80f373b8 Mon Sep 17 00:00:00 2001 From: Francesco Vigliaturo Date: Mon, 18 Nov 2024 11:42:17 +0100 Subject: [PATCH 1/3] add note for profiles stack trace rules --- .../event-grouping/stack-trace-rules.mdx | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx b/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx index 674cb9d137ac8e..79fc315ac1844f 100644 --- a/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx +++ b/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx @@ -6,6 +6,22 @@ description: "Learn how to use stack trace rules to group incoming events based + +A subset of stack trace rules, when defined, will also be applied to incoming profiles in order to improve the frames classification (in-app vs system). + +More specifically, only the rules with any of these matchers and actions (below) will be applied to profiles. + +Matchers allowed: + `stack.abs_path` + `stack.module` + `stack.function` + `stack.package` + +Actions allowed: + `+app` + `-app` + + If you use stack traces for grouping, the stack trace rules (previously known as _grouping enhancements_) influence the data that's fed into the grouping algorithm. These rules can be configured on a per-project basis in **[Project] > Settings > Issue Grouping > Stack Trace Rules**. Each line is a single rule; one or multiple match expressions are followed by one or multiple actions to be executed when all expressions match. All rules are executed from top to bottom on all frames in the stack trace. From a9a000596a815213cb2250c1bf6ba5ba784ed4ff Mon Sep 17 00:00:00 2001 From: Francesco Vigliaturo Date: Mon, 18 Nov 2024 15:38:11 +0100 Subject: [PATCH 2/3] add missing bullet marker --- .../event-grouping/stack-trace-rules.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx b/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx index 79fc315ac1844f..cee43b8838de75 100644 --- a/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx +++ b/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx @@ -12,14 +12,14 @@ A subset of stack trace rules, when defined, will also be applied to incoming pr More specifically, only the rules with any of these matchers and actions (below) will be applied to profiles. Matchers allowed: - `stack.abs_path` - `stack.module` - `stack.function` - `stack.package` + * `stack.abs_path` + * `stack.module` + * `stack.function` + * `stack.package` Actions allowed: - `+app` - `-app` + * `+app` + * `-app` If you use stack traces for grouping, the stack trace rules (previously known as _grouping enhancements_) influence the data that's fed into the grouping algorithm. These rules can be configured on a per-project basis in **[Project] > Settings > Issue Grouping > Stack Trace Rules**. From 85d939af542b21f3e552d52510c1e3bd648f986e Mon Sep 17 00:00:00 2001 From: Francesco Vigliaturo Date: Tue, 19 Nov 2024 11:52:33 +0100 Subject: [PATCH 3/3] address feedback and remove note --- .../event-grouping/stack-trace-rules.mdx | 24 ++++++++++--------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx b/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx index cee43b8838de75..3b08813980124c 100644 --- a/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx +++ b/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx @@ -6,25 +6,27 @@ description: "Learn how to use stack trace rules to group incoming events based - -A subset of stack trace rules, when defined, will also be applied to incoming profiles in order to improve the frames classification (in-app vs system). +Stack trace rules improve issue tracking by ensuring accurate grouping and better classification of stack frames as in-app or system. This helps focus on relevant code, reduces noise, and minimizes false positives. By tailoring rules to your project, you can streamline debugging and maintain consistency across teams or multiple applications. + +When you set stack trace rules (previously known as _grouping enhancements_) for grouping in Sentry, they influence the data that's fed into the grouping algorithm. These rules can be configured on a per-project basis by going to your project settings and then clicking on "Issue Grouping". + +Here are a few things to note about stack trace rules: + +- Each rule is written on a single line. +- Rules consist of one or more match expressions followed by one or more actions triggered when all expressions match. +- Rules are applied sequentially, from top to bottom, across all frames in the stack trace. -More specifically, only the rules with any of these matchers and actions (below) will be applied to profiles. +In addition, the stack trace rules using the below matchers and actions can also be applied to incoming profiles to improve frame classification (in-app vs system, for example). -Matchers allowed: +Allowed Matchers: * `stack.abs_path` * `stack.module` * `stack.function` * `stack.package` - -Actions allowed: + +Allowed Actions: * `+app` * `-app` - - -If you use stack traces for grouping, the stack trace rules (previously known as _grouping enhancements_) influence the data that's fed into the grouping algorithm. These rules can be configured on a per-project basis in **[Project] > Settings > Issue Grouping > Stack Trace Rules**. - -Each line is a single rule; one or multiple match expressions are followed by one or multiple actions to be executed when all expressions match. All rules are executed from top to bottom on all frames in the stack trace. The syntax for stack trace rules is similar to: