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 spam folder ….nada. no email.
A few seconds later I got a notification (configured to send to Slack at the moment, we support Microsoft Teams / Email and Generic Webhook endpoints) informing me about the issue:
Clicking the link opens the error bucket page (for deeper discussion about Error bucket and root causes please see this blog
For the first time I’m happy that something is not working, and this is why we’ve built railtown.ai in the first place.
To summarize railtown.ai was able to help with:
railtown.ai helped us go from the notification to a fix for the issue quickly!
If you don’t already have a railtown.ai account sign up and let us help you improve the quality of your software and increase your developer velocity.
Railtown.ai helps you gather the information you need to efficiently resolve an error, but by combining our application with other tools can take your developer workflow to the next level. So today, we’d like to go through 2 popular tools that we recommend for expanding your team’s capabilities: New Relic and Azure Application Insights.
Too many software development teams treat error logging as a burden rather than a chance to grow.That’s why Jeli’s “Howie: Post-Incident Guide” felt like a breath of fresh air. In the guide, Jeli’s team notes that negative treatment of bugs is everywhere, including the language we use to describe software development. Terms like “post-mortem” and “root-cause analysis” speak for themselves.We’d like to build on the suggestions put forward in Howie and share our perspective on error logging as well. So let’s take a look at how a small mindset shift around debugging could encourage more positive moments in your team.
Plenty of developers who start coding in Node.js do so because of how easy it is to get started. But once you are ready to take your application to the next level, you need to take a step back. Why did you choose to build in Node.js, and where do you want to take your application from here? To scale your Node.js application, you need to figure out just how to use performance monitoring to your advantage.