(OP here) Thanks for bringing this up – we definitely took inspiration from Sentry Breadcrumbs and actually use this feature in our apps quite a bit.
We found that many bugs are not easily understood by looking at the breadcrumbs trail. Our goal is to give developers all of the context that is needed for fixing bugs: a video, steps to reproduce, and eventually a way to faithfully restore the state of an app at the exact point of failure.
Our goal is not to compete with Sentry, but rather to augment crash reporting tools with a tool dedicated to logging.
I don't really like how the prominent "Open Source" link at the top takes me to a page on github telling me it's currently not open source. I'd have assumed they'd "work out the kinks" faster if the source code was actually open and available.
(OP here) Hey kingosticks, appreciate this and trust me that I'd love to open source this ASAP.
We're just working out our deployment story and making sure that it can scale before we open source. We don't want to force beta users to go through painful upgrades / migrations unless absolutely necessary.
(OP here) Thanks for asking this toni, as privacy issues are one of the reasons that we felt that this tool was necessary.
We want to give developers the ability to solve bugs without compromising user security. You can choose exactly what gets logged, and also host on your infrastructure. We're also building tools for anonymizing data that is sent over the wire.
Hi there.
I'm the Co-founder of SessionStack - https://www.sessionstack.com/ .
Seems like you're developing quite the same tool (we're not open source, but have an on-premises version).
It's quite an interesting space so I wish you good luck in your endeavor.
16 comments
[ 3.4 ms ] story [ 42.8 ms ] threadWe found that many bugs are not easily understood by looking at the breadcrumbs trail. Our goal is to give developers all of the context that is needed for fixing bugs: a video, steps to reproduce, and eventually a way to faithfully restore the state of an app at the exact point of failure.
Our goal is not to compete with Sentry, but rather to augment crash reporting tools with a tool dedicated to logging.
I'm sure the implementation is different but be 'inspired' don't shamelessly clone their design.
https://help.github.com/articles/name-squatting-policy/
EDIT: Although, maybe it's all private activity, which I guess is not visible to the likes of me.
We're just working out our deployment story and making sure that it can scale before we open source. We don't want to force beta users to go through painful upgrades / migrations unless absolutely necessary.
And don't forget that painful (exciting) upgrades is exactly what some beta users are signing up for in the first place!
We want to give developers the ability to solve bugs without compromising user security. You can choose exactly what gets logged, and also host on your infrastructure. We're also building tools for anonymizing data that is sent over the wire.
"If your work isn't ready for people to try out yet, please don't do a Show HN. Once it's ready, come back and do it then."
It's quite an interesting space so I wish you good luck in your endeavor.