Sentry: Search by source code context or filename (from frame)

[benvinegar]

Basically, the ability to locate an error by searching for affected source code, i.e. a function call or particular variable.

[dharaburda]

This would be useful. It seems like just being able to search the text of the stack trace would cover most cases...

[DavidDuwaer]

Why is this issue so quiet? For me this is hugely important. It is the single most important reason to get all my exceptions in 1 place: so I can search them properly. And searching by a string occuring in a stacktrace is vital in that. When there are bugs happening with a certain component of an application, the first thing you want to do is search the names of the relevant classes/functions in Sentry, and Sentry would show in which Exception-stacktraces this class or function shows up.

Consider for example a webhook failing to take all notifications for some unknown reason. You would go to Sentry, and search for the name of the relevant controller(-method) of that endpoint, and any failure not just of the class or method itself, but _also of any subroutine_, would pop up in the search results. Exceptions bubble up, remember, subroutines crash parent routines, so failures of subroutines are just as relevant. If we could do this it would be enormously powerful in debugging issues on a production environment.

I'm not in this project and so don't know anything about its intricacies, so please correct me if I'm wrong about any assumptions here, but I'm just wondering because from a distance, implementation seems fairly straightforward. If you, for this function, treat the entire stacktrace as a piece of text, this text can just be added to the set of text fields searched by the full text search. Is it that Sentry does not have a full text search component, and is that why this issue is harder to make?

[kirik]

I just found myself to be able to search by exception stacktrace via Discovery tool. Query looks like stack.function:*main* or stack.filename:**/main.cpp. Maybe this workaround will help a little.

[tsondergaard]

This issue can be closed. The feature was added long ago as @kirik points out.