We have some exciting news: thanks to our friends at Honeybadger, we now have a public dashboard that collects runtime bugs on DEV!
If you'd lik...
For further actions, you may consider blocking this person and/or reporting abuse
Let's kill the bugs !
I've always been a Rollbar person, but I have some friends sware by Honeybagder.
Maybe I'll fix a few bugs so I get to experience the other side of error reporting service.
I noticed in my blogs, I used the
source code'
' for a lot ofthings, and this breaks the rendering veryeasily`.Awesome
Are you worried about any sensitive information being leaked in error logs and exceptions? I know we all do our best to keep PII and secrets out of logs, but this feels like it could be a bit risky! 😱
Hi Tim, we do collect a lot of data that could potentially have PII (such as request parameters and session data). For this reason, public dashboards are limited to just a few pieces of information about each exception: the class name, error message, and backtrace. It is still technically possible to leak information in the error message or other fields (it's obviously really bad practice to include PII in an error message, but it does happen). However, each error on the public dashboard was specifically shared by a DEV team member with full account access, which implies that the error data was reviewed first. (It's similar to copy/pasting the error information into a GitHub issue which is what they were doing before).
Does that help? I'm happy to answer any other questions or discuss concerns you may still have.
Thanks for the detailed response! Sounds good!
This is great! Time to check some bugs out.