Sentinel is your on call engineer to investigate and fix any issue Sentry detects in your project. Connect to Slack to get instant responses on any Sentry alert with an explanation of: - What the error is - Why the error happened - What the best fix is
Sourcery AI
Hey ProductHunt!
Does your team ever feel overwhelmed by the number of alerts about bugs/issues coming out of tools like Sentry?
We built Sentinel to be your team's on-call engineer who can help you work your way through high volumes of issues, investigating every alert as it comes in, telling you which ones you can ignore and which to fix, and directly fixing the straightforward issues for you.
If you connect Sourcery Sentinel, Sentry, and GitHub we'll immediately start investigating your 50 most recent issues and investigate new issues as they come in. On every issue we'll give you an in depth walkthrough of why the error happened - from flagging the potential commit that caused it, to highlighting the line(s) of code that are giving you a problem, to pointing out a data integrity problem.
If you're like us and get Sentry alerts in Slack you can link Sentinel into your Slack channels and we'll respond directly to every thread with an explanation of what's gone wrong and how to fix it.
Let us know what you think and how we can keep making it easier for your team to handle bugs and production issues!
Very cool! Love the idea. And was literally just yesterday talking about it with @jerome_bau. Does this also work if I'm on GitLab instead of GitHub?
Sourcery AI
@lukas_kemkes no GitLab support quite yet, but it's on the roadmap!
Sourcery AI
This was a ton of fun to build!
Like a lot of teams our Sentry alerts had become a source of noise, and we really wanted to be able to clean them out and fix our backlog of issues without spending a ton of time.
We had been starting to develop a software agent, and realised that we could hook it in to investigate the issues for us.
It's the slack integration that really makes it - the first time we got an alert from Sentry and then Sourcery replied with the cause, the suspect commit and a fix that just worked was pretty magical.