Extend grouping and fingerprinting rules for native use-cases

[mujacica]

Problem Statement

Match sibling frames Fingerprint

Situation:

• Fingerprints and stack trace rules aren't using the same grammar
• Matching sibling frames is not available for fingerprint rules

Problem:

• If a developer crashes the game through a debug command, there are two frames that are needed to group on (if HandleDebugCommand and ExecuteError -> debugcrash)
• That's not possible without sibling frames matching

Proposed Solution:

• Extend fingerprint rules to allow sibling frames matching syntax (similar to stack trace rules)

Thread-based fingerprint rules

Situation:

• For larger games that are integrating with multiple external and 3rd-party libraries
• Using fingerprint rules it's possible to group them all in the same issue (only using path), but not more granularity is given (e.g. in which thread the crash happened)

Problem:

• Crashes that happen in the same library/code with a similar stack trace, but on completely different threads, performing different tasks get grouped together.

Proposed solution:

• Extend fingerprint/grouping rules to allow filtering on specific threads (e.g. named vs. unnamed threads, specific thread name, etc.) and on binary/executable names
• Create a grouping rules that take thread into account when grouping issues (e.g. crash on MainThread:Function vs WorkerThread:Function not grouped together)

Solution Brainstorm

No response

Product Area

Issues

[linear]

ENG-5822

[mujacica]

Prototype draft to review with grouping team: #102653