From b90ad5685c57e1f0ff717948ff89ee86b9c21676 Mon Sep 17 00:00:00 2001 From: Hector Date: Wed, 11 Feb 2026 13:41:28 +0000 Subject: [PATCH] Link directly to Issue Grouping Resolves DOCS-A9C --- .../data-management/event-grouping/fingerprint-rules.mdx | 2 +- .../data-management/event-grouping/stack-trace-rules.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/data-management/event-grouping/fingerprint-rules.mdx b/docs/concepts/data-management/event-grouping/fingerprint-rules.mdx index caba4f2d3bdd8..563a4628a48df 100644 --- a/docs/concepts/data-management/event-grouping/fingerprint-rules.mdx +++ b/docs/concepts/data-management/event-grouping/fingerprint-rules.mdx @@ -8,7 +8,7 @@ description: "Learn about fingerprint rules, matchers for fingerprinting, how to Fingerprint rules (previously known as _server-side fingerprinting_) are configured with a config similar to [stack trace rules](../stack-trace-rules/), but the syntax is slightly different. The matchers are the same, but instead of flipping flags, a fingerprint is assigned and it overrides the default grouping entirely. Assigning a fingerprint can also refine the default grouping rather than overriding it, if the fingerprint includes the value `{{ default }}`. -These rules can be configured on a per-project basis in **Project Settings > Issue Grouping > Fingerprint Rules**. This setting has input fields where you can write custom fingerprinting rules. To update a rule: +These rules can be configured on a per-project basis in your project's [Issue Grouping](https://sentry.io/orgredirect/organizations/:orgslug/settings/projects/:projectId/issue-grouping/) settings. This setting has input fields where you can write custom fingerprinting rules. To update a rule: 1. Identify the match logic for grouping issues together. 1. Set the match logic and the fingerprint for it. 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 e496e3587717d..a80299d2b9564 100644 --- a/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx +++ b/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx @@ -8,7 +8,7 @@ description: "Learn how to use stack trace rules to group incoming events based 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 in **Project Settings > Issue Grouping > Stack Trace Rules**. +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 in your project's [Issue Grouping](https://sentry.io/orgredirect/organizations/:orgslug/settings/projects/:projectId/issue-grouping/) settings. Here are a few things to note about stack trace rules: