4 ms·
The thing I love the most about Sentry/Bugsnag/Honeycomb/etc is that it is essentially automated observability. That is, I don't need to do a huge amount of int
by mark242 2y ago
The thing I love the most about Sentry/Bugsnag/Honeycomb/etc is that it is essentially automated observability. That is, I don't need to do a huge amount of integration to have, basically, a prioritized list of bugs along with severity and overall application health.
I like the idea of the browser extension being able to offer these kinds of tools where you wouldn't need to install a heavy Javascript snippet -- but I do think that taking the manual steps out of debugging wherever you can is the most efficient. With Bugsnag et al, I don't need to wait for a user to contact me. I shouldn't have to wait for someone to submit a Jam report in order to see how healthy my app is.
- wjdp 2y agoI see these tools as complimentary. Sometimes Sentry &al don't capture a user session (blocking, didn't consent &c) and this tool acts as a nice fallback you can instruct the user to use rather than having to explain how to open dev tools and screenshot the console.
- gbalduzzi 2y agoI think they serve different purposes. Sentry/Bugsnag etc track code errors and exception. But sometimes for an user an error is not a code exception, but the software having the wrong behaviour. Some examples: > "The button brings me to the wrong page" > "I filled out the whole form but the submit button is not enabled" > "The video should autoplay but is stuck loading" Those things do not show up in Sentry logs.
- a_t48 2y agoSentry has session replay that should catch all of these things - it doesn't look any higher friction than this tool.
- gbalduzzi 2y agoOnly if an exception is raised. The alternative is to record every user session, resulting in a privacy mess. This tool allows the reporter to select when data should be collected