• EnglishEspañol日本語한국어Português
  • Log inStart now

Troubleshoot browser instrumentation in Node.js


If you've problems instrumenting browser applications via your New Relic Node.js agent, follow the standard troubleshooting procedures. Here are some additional tips for Node.js.


Error codes will automatically appear in the site source code and in your Node.js agent logs. Search for NREUM to find these codes.

Error code



Browser monitoring has been explicitly disabled. This was done either in the newrelic.js or with an environment variable. (NEW_RELIC_BROWSER_MONITOR_ENABLE defaults to true.)


The browser agent was called outside of a web transaction. This may occur if you tried to generate the browser data once and then cache it, or if you called it in a background task.


Something unexpected occurred.


The transaction is unnamed. If you are not using Express or Restify and you did not explicitly name the transaction, this error appears. This is to avoid rolling the transaction name into **/***. For more information, see naming your transactions.


The Node.js agent has not yet done a "handshake" with the collector. The app was started and a user hit the site before the collector could talk to the agent. This may occur because:

  • The browser page loaded before the agent made its initial connection to New Relic.

  • The license key is invalid.

  • Some other problem occurred that would prevent the application ID from being available.

    If these errors persist longer than 1 minute, check your . Otherwise, the errors should disappear on their own.


Browser monitoring has been disabled on the collector side. For example, the collector did not return enough data for browser monitoring to be enabled. This is a collector issue, because some server-side configuration settings for Node.js currently are not available.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.