Integrating Azure DevOps CI/CD pipeline with Conductr AI
Integrating your application with Conductr AI involves the following 3 things: Sending your logs to Conductr, covered in other blog posts Letting Conductr know when you successfully complete a build and when you deploy the build to an environment, covered in this blog post Integrating with your ticketing system so that Conductr can pull your ticket […]
Root Cause Discovery for NodeJS
Conductr is happy to announce that root cause discovery is now available for teams that run on NodeJS. This is exciting for full stack developers who utilize javascript because they can integrate with Conductr on the frontend and backend. Conductr has integrated with the most popular logging libraries including Winston, Bunyan, Pino, Log4js, and […]
Root Cause Discovery for JavaScript
We are very excited to announce the release of Railtown Root Cause Discovery for Javascript. The team has been working hard to add javascript to the list of technologies that Railtown supports and is able to expose its Machine Learning platform to. This will allow teams visibility into the health of their application from the […]
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 […]
