Root Cause Discovery for NodeJS

by

Chris Girard

September 6, 2022

3 Min

reads

Railtown 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 railtown on the frontend and backend.


Railtown has integrated with the most popular logging libraries including Winston, Bunyan, Pino, Log4js, and LogLevel. If your team is already using one of these logging packages then integration is super simple. If not we recommend trying Winston and adding the winston-railtown package.


The logging libraries we support allow you to send your logs to a custom destination through a method called a transport. The railtown packages are custom build to add a railtown transport for each library.


Each logging library has different configurations but with Winston, for example, its easy to turn on detection for handling uncaught exceptions as well as uncaught promise rejections. You can also specific custom errors anywhere in your code and they will be sent to railtown with the full stack trace.


What is great is that you can now see frontend javascript errors as well as NodeJS errors in the same project and quickly discern between them.

To quickly get started stated head over to railtown.ai to signup for a free account and grab your token. Then select the logging library of your choice and add railtown as a destination.

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. Now we can support your full stack!

Keep reading

AppInsightsBest Tools to Integrate with Railtown.ai

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.

by

Marwan Haddad

January 6, 2023

5 Min.

reads

CultureHow to Build a Positive Culture Within Development Team on Debugging

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.

by

Marwan Haddad

December 1, 2022

5 Min

reads

Error BucketNode.js Monitoring: Performance Monitoring Best Practices

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.

by

Marwan Haddad

November 21, 2022

5 Min

reads