This document describes the New Relic Node.js agent attributes, details how to enable or disable attributes, and describes the rules the agent follows to determine which attributes to include or exclude for a destination.
These attribute settings apply to Node.js agent version 2.7.1 or higher. If you use an older version of the agent, see Update legacy attribute configuration.
New Relic attributes are key-value pairs containing information that determines the properties of event and transaction data. Attributes can help you gain greater insight into your application and annotate the data in New Relic.
Attributes (both default and custom) can be found in:
You can customize exactly which attributes will be sent to each of these destinations.
As of Node.js agent version 6.10.0, when you enable distributed tracing and/or Infinite Tracing, information from
Transaction events is applied to the currently available
Span of the transaction. Because of this, you may want to apply the attribute settings for
Transaction events to
Span events or apply them as global attribute settings.
In addition to the default APM attributes, the Node.js agent collects attributes from these sources:
You can customize what types of attributes the Node.js agent sends to each destination. This is most common for security reasons, when you have certain sensitive attributes you do not want reported to New Relic.
Use the following configuration properties along with the attribute rules to enable or disable attributes:
The Node.js agent follows these rules when determining which attributes to include or exclude for a destination:
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.