Operations | Monitoring | ITSM | DevOps | Cloud

Sometimes developers are hesitant to include logging due to performance concerns, but is this justified? And how much does library choice affect performance? The team at SolarWinds® Loggly® and myself decided to find out. We ran a series of performance tests on some of the most popular Node.js libraries. These tests are designed to show how quickly each library processed logging and the impact on the overall application. Let’s see how they did!

Serverless architectures such as AWS Lambda have created new challenges in debugging code. Without a solid logging framework in place, you could waste hours, or even days, tracking down simple defects in your functions. A strategic logging framework can be a powerful way to track down and resolve bugs. Let’s walk through how to get the most out of logging Lambda functions.

When your customers depend on your data 24/7, you must know what your applications are doing at any given time and be able to troubleshoot quickly. That’s why Traxo implemented the SolarWinds® web application performance monitoring (APM) portfolio. Traxo provides itinerary intelligence and travel data aggregation technology solutions to companies across the travel ecosystem.

Winston is one of the most popular and versatile logging libraries for Node.js. With Winston, you can differentiate and redirect your logs to different places depending on their severity or purpose, and ensure there are redundant records in case of any failures or corruption later on. With the Winston 3.0 update, one of the biggest changes is the ability to apply custom formatting to your logs.