If you have encountered any of these common problems after installing your New Relic Node.js agent, try these troubleshooting tips.
Some common problems users encounter after installing the New Relic Node.js agent include:
To minimize the amount of bandwidth the Node.js agent consumes, New Relic only reports data once per minute. If you add the agent to tests that take less than a minute to run, it will not have time to report data to New Relic.
If you do not see transaction traces or other data after deploying the agent, this may be due to configuration, framework, or Apdex settings. Use New Relic Diagnostics to try to automatically identify the issue.
What to check
Ensure that you
If you cannot control how your main module is run, ensure that you have added
If you have any conditional logic in your
For problems with supported frameworks, make sure you are using Connect, Express, Hapi, Kraken, or Restify. There are other Node.js frameworks, but New Relic does not support all of them.
The agent can collect VM metrics related to garbage collection (GC), memory, and CPU. Some of these metrics require an additional native module to be installed.
Here are some common problems and their solutions:
During installation, npm shows one of the following error messages:
gyp ERR! configure errorgyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! build errorgyp ERR! stack Error: not found: make
make: g++: Command not found
Ensure that the prerequisites for the
node-gyp module are installed. On Debian/Ubuntu platforms, use this command:
$apt-get install build-essential
For more information, see Node.js VM measurements.
Other troubleshooting resources on our Support Forum forum: