Issue
I want to know why frames from my internal package or library are marked as system (not in-app) in the stack trace.
Applies To
Frames missing from Most Relevant
Frames greyed out / treated as non–in-app
Symptoms
Frames you wish to see do not show under "Most Relevant"
Frames you wish to see with full context are greyed out
Resolution
By default, dependency paths are marked as non-in-app - for example, **/node_modules/** in JavaScript or **/site-packages/** in Python. This can also affect your own package if it lives under one of those paths.
You can override this with a project Stack Trace Rule under Project Settings → Issue Grouping. Rules are applied top to bottom. For example, to mark a package under node_modules as in-app:
stack.abs_path:**/node_modules/YOURPACKAGE/** +app
You can also mark packages as in-app directly in the SDK using options such as in_app_include or inAppIncludes.
See Stack Trace Rules and your platform’s SDK options for more details.