search

vanjacosic / opbeat-js

An experimental JS client for logging exceptions and stacktraces to Opbeat
BSD 2-Clause "Simplified" License
11 stars 1 forks source link

Handle stacktraces with fingerprinted files #4

Open paulcwatts opened 9 years ago

paulcwatts commented 9 years ago

I've been using this now for a few weeks and it seems to work well. However, there is still an issue with effectively grouping errors based on stacktraces, since it's using fingerprinted file paths. As soon as we release a new build, the same errors appear as new groups because the file paths appear different.

screen shot 2015-07-21 at 5 05 40 pm

I'm not sure how to handle this generically, other than possibly allow the caller to normalize the file paths before sending to Opbeat?

roncohen commented 9 years ago

Hey Paul. Are you building sourcemaps?

paulcwatts commented 9 years ago

We are, but we're currently not doing anything with them. That's primarily due to a lack of process and tooling than anything. If we could upload them to Opbeat, that'd be awesome.

roncohen commented 9 years ago

OK. As far as i know, the usual thing to do it to upload them to the webserver, next to the "uglified" files. Opbeat would then download them from there and try to make sense of it. Unfortunately, It's not something we're currently looking at.

paulcwatts commented 9 years ago

I wouldn't want them to be publicly accessible. Other tools I've seen allow you to upload them into their service or allow them to be kept private.