From the Blogosphere
Analyze Node.js Errors Down to the Code Level By @MiKopp | @DevOpsSummit #APM #DevOps
Ruxit marks web requests to Node.js as failed based on the accompanying HTTP error code
By: Dynatrace Blog
Aug. 2, 2015 11:00 AM
Analyze Node.js Errors Down to the Code Level
Beginning with Ruxit Agent v1.73, Ruxit provides root cause analysis for Node.js errors down to the code level. As with other services, Ruxit marks web requests to Node.js as failed based on the accompanying HTTP error code.
Simply click the Failure rate portion of any Node.js service infographic to view the Failure analysis chart. If you have failures, click the View details of failures button to see which requests failed along with an overview of failure reasons sorted by HTTP code. You can select a single request to focus on.
At the bottom of the screen you’ll see the exceptions that are the root causes of the selected failure and request. Click any Details button to view a list of exception messages and associated stacktraces.
Ruxit doesn’t simply show you a list of exceptions. As you can see below, Ruxit shows you the root causes. For example, all failed requests to /error-4 were caused by a single exception in a single line of code!
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week