Browser Monitoring & SSL Arrives for Node.js

Hot on the heels of last week’s amazing browser monitoring feature announcement, the Node.js team here at New Relic is excited to let you know that the agent now has the power of browser monitoring.

This rounds out New Relic’s browser monitoring offering to all 6 of our language agents (Ruby, Java, .NET, PHP, Python and Node.js).

In case you missed the the blog post last week, the new browser monitoring features include:

  • Javascript Errors
  • AJAX Timings

This data is now visible in New Relic, giving you a client-side view into your application like you’ve never seen before.┬áThese features are in beta and available alongside our existing RUM features.

Sam image 1

SSL for Node, too!

In addition to browser monitoring on Node.js, we’re are also adding SSL to the agent and enabling it by default.

New Relic takes your privacy very seriously and though we always strive to be secure by default, as we add more opt-in features to the agent like custom metrics or custom parameters, for instance, it’s obvious that this data should only end up at New Relic.

Get started with Browser Monitoring on Node.js

The first step to get browser monitoring up and running in your Node app is to take a quick read of the docs. You’ll need to add one API call to your templates and you’re good to go. We’ve got examples for Express with Jade or Swig as well as Hapi and Handlebars.

Once you’ve had a chance to play around with it awhile, we’d love to hear about it on the new New Relic Node Discussion Board.

Nate Heinrich is a product manager at New Relic. He has a background in IT management, Web development, and operations. His hobbies include sports that include balls and nets, games of the video variety, and experimenting with machine learning APIs to one day predict something useful. View posts by .

Interested in writing for New Relic Blog? Send us a pitch!