July 22nd, 2014 • By Brian Rue
We've released several new search filters to make it easier to find errors by the filenames in their stack trace. If you've ever wanted to find client-side Angular JavaScript errors that only occurred within your own specific domain, or exceptions originating in a specific part of your code, keep reading.
You've always been able to search for errors where any filename contains a string, but now you can also search for errors where:
allfiles:myproject
)nofiles:evilproject
)topfile:mydomain.com
)bottomfile:some_important_library
)minfiles:1
and/or maxfiles:10
)file:.rb
)These filters can all be combined in a single query. If you forget which filters exist, mouse over the ? next to the search box to see the help text.