Native Metrics for New Relic Node.js Agent

This module provides hooks into the native layer of Node.js to provide metrics for the New Relic Node.js Agent. It gathers information that isn't available at the JS layer about the V8 virtual machine and the process health. It comes packaged with the New Relic Agent since v2, and there is nothing that needs to be done. For Agent v1 you need only to install the module alongside newrelic.

Installation and Getting Started

Typically, most users use the version auto-installed by the agent.

In some cases, installing a specific version is ideal. For example, new features or major changes might be released via a major version update to this module, prior to inclusion in the main New Relic Node.js agent.

$ npm install --save @newrelic/native-metrics

Note that this is a native module and thus must be compiled to function. Pre-built binaries are included in the package for the following platforms, across all LTS versions of Node.js:

• Linux/amd64
• Linux/arm64
• macOS/arm64
• Windows/x64
• Windows/x86

If your system does not match the above matrix, you will need to have a compiler installed on the machine where this is to be deployed. See node-gyp for more information on compiling native addons.

If you prepare and package deployments on one machine and install them on another, the two machines must have the same operating system and architecture. If they are not, you will need to re-build the native module after deploying in order to get the correct binaries.

During installation, the module will first attempt to locate a prebuilt binary for the target machine within its included list of prebuilt binaries. If that fails, it will attempt a standard node-gyp build. If you do not want to use prebuilt binary, or know that it will need to be built, you can force a build:

$ npm install @newrelic/native-metrics --build-from-source

For more information, please see the agent installation guide and compatibility and requirements.

Musl Libc Systems

As noted above, this module ships pre-built binaries for most standard systems, i.e. systems based on the GNU C Library. As of August 2024, Node.js does not provide "official" releases that are based on musl libc; such builds are only available via the unofficial builds project. Therefore, if deploying to musl based systems, e.g. Alpine Linux, you must provide a node-gyp compatible build environment.

As an example, to install and use this module on an Alpine Linux based Docker image, we can utilize the multi-stage build pattern to build a compatible image:

package.json:

{
  "dependencies": {
    "@newrelic/native-metrics": "^11.0.0"
  }
}

index.js:

'use strict'

const metrics = require('@newrelic/native-metrics')
console.log("gcEnabled:", metrics().gcEnabled)

Dockerfile:

FROM node:20-alpine AS builder

WORKDIR /app
COPY index.js package.json .

RUN apk add g++ make py3-pip
RUN npm install --production

FROM node:20-alpine
COPY --from=builder app/ /app/
WORKDIR /app
CMD node index.js

With those files in place, we can build and run the image:

$ docker build --tag demo .
$ docker run --rm -it demo
gcEnabled: true

Usage

var getMetricEmitter = require('@newrelic/native-metrics')

var emitter = getMetricEmitter()
if (emitter.gcEnabled) {
  setInterval(() => {
    var gcMetrics = emitter.getGCMetrics()
    for (var type in gcMetrics) {
      console.log('GC type name:', type)
      console.log('GC type id:', gcMetrics[type].typeId)
      console.log('GC metrics:', gcMetrics[type].metrics)
    }
  }, 1000)
}
if (emitter.usageEnabled) {
  emitter.on('usage', (usage) => console.log(usage))
}
if (emitter.loopEnabled) {
  setInterval(() => {
    var loopMetrics = emitter.getLoopMetrics()
    console.log('Total time:', loopMetrics.usage.total)
    console.log('Min time:', loopMetrics.usage.min)
    console.log('Max time:', loopMetrics.usage.max)
    console.log('Sum of squares:', loopMetrics.usage.sumOfSquares)
    console.log('Count:', loopMetrics.usage.count)
  }, 1000)
}

The metric emitter keeps a referenced timer running for its periodic sampling events. For a graceful shutdown of the process call NativeMetricEmitter#unbind.

getMetricEmitter().unbind() // Process will now close gracefully.

If you would like to change the period of the sampling, simply unbind and then call NativeMetricEmitter#bind with the new period.

var emitter = getMetricEmitter({timeout: 15000})
emitter.unbind()
emitter.bind(10000) // Samples will now fire once every 10 seconds.

Testing

This module includes a list of unit and functional tests. To run these tests, use the following command

$ npm run test

You may also run individual test suites with the following commands

$ npm run unit
$ npm run integration

Support

Should you need assistance with New Relic products, you are in good hands with several support channels.

If the issue has been confirmed as a bug or is a feature request, please file a GitHub issue.

Support Channels

• New Relic Documentation: Comprehensive guidance for using our platform
• New Relic Community: The best place to engage in troubleshooting questions
• New Relic Developer: Resources for building a custom observability applications
• New Relic University: A range of online training for New Relic users of every level
• New Relic Technical Support 24/7/365 ticketed support. Read more about our Technical Support Offerings.

Privacy

At New Relic we take your privacy and the security of your information seriously, and are committed to protecting your information. We must emphasize the importance of not sharing personal data in public forums, and ask all users to scrub logs and diagnostic information for sensitive information, whether personal, proprietary, or otherwise.

We define "Personal Data" as any information relating to an identified or identifiable individual, including, for example, your name, phone number, post code or zip code, Device ID, IP address and email address.

Please review New Relic’s General Data Privacy Notice for more information.

Roadmap

See our roadmap, to learn more about our product vision, understand our plans, and provide us valuable feedback.

Contribute

We encourage your contributions to improve Native Metrics for the New Relic Node.js Agent! Keep in mind when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project.

If you have any questions, or to execute our corporate CLA, required if your contribution is on behalf of a company, please drop us an email at opensource@newrelic.com.

To all contributors, we thank you! Without your contribution, this project would not be what it is today.

If you would like to contribute to this project, please review these guidelines.

A note about vulnerabilities

As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.

If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.

License

The Native Metrics for New Relic Node.js Agent package is licensed under the Apache 2.0 License.