If you have problems instrumenting browser applications via your New Relic Node.js agent, follow the standard browser monitoring 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.
Browser monitoring has been explicitly disabled. This was done either in the
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:
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.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.