Sequential Errors and Azure Search
Conductr offers powerful error handling tools that make debugging easier for developers. Instead of receiving hundreds of notifications for the same error, Conductr will group errors together and “bucket” them for easier management. Sometimes developers need to investigate errors sequentially and see what events occurred immediately before and after a specific error. Along with […]
Integrating with Application Insights
In this blog post we’re going to cover how you can use Conductr to get extra value from the telemetry you are already collecting with Application Insights. First off, if you are using a logging framework, like Serilog, to collect logs and then forward them to Application Insights via a sink, then you can simply […]
For the first time I’m happy that something is not working
It’s 2pm and I am in a meeting with a UI/UX designer to help us design a few new interactions on the platform. I go to the project settings page to invite the designer. I enter their email address in the invitations, they don’t get the email. I resend the invite, nothing. They check the […]
Introducing ticket matching service
In our first blog post “Error Buckets and Root Causes”, you learnt how Conductr helps you analyze and group errors that belong to the same error bucket. The story doesn’t stop there. In this blog post, you will learn how Conductr uses AI and Machine learning to identify tickets/work items that might have caused the […]
Error Buckets and Root Causes
I’m sure anyone out there using redis has probably seen log output like this from time to time: Users can’t sign up… and our payment processor is failing… and users can’t login… and our SSO is broken! A low-level exception is bubbling all the way up and it looks like we have lots of issues […]
