Better Transaction Names #488
Description
Sentry has the concept of 'culprit' today, but we're likely going to move to a transaction name pattern. I dont think we'll be renaming the attribute as part of this, but the goal will be to provide a native API within clients to override it using a stack approach (see Python draft).
That is, if you're using Rails, the transaction might be the route name (or the route class that handles it, rather), instead of some semi-arbitrary function in the stacktrace.
Wanted to open this issue to begin discussion on what would fit best there.
For reference, the current culprit that would be replaced shows up similar to app/foo.rb in block in blah at line 13.