You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rails backtraces can be very verbose. This not only leads to noisy traces where it is difficult to find relevant information, but it also interferes with how effectively periskop is able to group exceptions (since it uses a maximum number of backtrace lines for efficiency reasons, see
Rails backtraces can be very verbose. This not only leads to noisy traces where it is difficult to find relevant information, but it also interferes with how effectively periskop is able to group exceptions (since it uses a maximum number of backtrace lines for efficiency reasons, see
periskop-ruby/lib/periskop/client/models.rb
Line 104 in 03e17f1
Rails introduced the concept of BacktraceCleaner a while ago, we should probably implement something similar, potentially configurable with some well known instances ready to use. See https://www.rubydoc.info/gems/activesupport/2.3.5/ActiveSupport/BacktraceCleaner for inspiration.
The text was updated successfully, but these errors were encountered: