Update Grouping Content#3776
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/sentry/sentry-docs/5Mhi3U5adwCSKGRiHLU6dhq2MAGR |
jan-auer
left a comment
jan-auer
left a comment
There was a problem hiding this comment.
The document is called "Issue Grouping", so since we're moving it already, I'd also use issue-grouping in the URL rather than event-grouping.
| @@ -1,10 +0,0 @@ | |||
| ```discover {tabTitle: Enhancement Rules} | |||
| # mark all functions in the std namespace to be outside the app | |||
| family:native stack.function:std::* -app | |||
There was a problem hiding this comment.
I'm realizing that these examples are actually useful. I completely missed that we had these customized. Do you have an idea on where or how we can keep them? Maybe keep a tiny section in the platform docs, and then link to product docs for full detail?
There was a problem hiding this comment.
Currently, on the product side of the house, the include statements don't work as they do for platforms. For now, we can add more examples and hard code them. In future, with more tools support, we can enable platform-specific support/include statements on the product side of our content.
| redirect_from: | ||
| - /data-management/rollups/ | ||
| - /learn/rollups/ | ||
| - /data-management/event-grouping/ |
There was a problem hiding this comment.
Shouldn't this redirect from the platform pages, or is that what it does?
There was a problem hiding this comment.
This is the location in which it used to reside.
2 participants
In preparation for future functionality, we're moving the grouping content into SDK-specific content and product content.
The SDK fingerprinting content now lives in Usage > SDK Fingerprinting. The data management content is now in product > Data Management > Issue Grouping. This also had the knock-on effect of removing a series of
includefolders that weren't really needed (as the product side doesn't currently support the use ofincludestatements).