Issue
Stack trace frames from an internal library or package are marked as system frames by Sentry.
Applies To
All Sentry users.
Symptoms
Frames you wish to see do not show under "Most Relevant"
Frames you wish to see with full context are greyed out
Resolution
Sentry has default stack trace rules in place to build out your "Most Relevant" stacktrace view. For example, in JavaScript we have a default rule:
stack.abs_path:**/node_modules/** -app
This rule sets all frames stemming from the node_modules folder as non in-app. Similarly, in Python, we have a default rule:
stack.abs_path:**/site-packages/** -app
Sometimes, these default rules can be too eager, and if you are importing your own package, you may wish for frames that come from your package to be marked "in app"
Set custom Stack Trace rules in the Issue Grouping settings of your project settings. Custom rules will always take precedence over the default rules. For example, referring to the JavaScript rule above, if there is one package you would like to allow, you can set a rule like this -
stack.abs_path:**/node_modules/{YOURPACKAGE}/** +appThe rule above will mark 1 defined package under the node_modules and mark it as "in app" (signified by the + symbol). All other frames from the node_modules folder will remain as marked "non in app"