Supported Data Types
📈 MetricsOverview
The New Relic source supports three different senders. Each sender uses a different protocol and collector endpoint.Note: The APM agent and Infrastructure agent are different products. Do not use the APM agent endpoint for the Infrastructure agent.Infrastructure-agent support is enabled by default on Sawmills Collector
v1.1097.0 or later. There is no source option to enable or disable this support.
As with all Sawmills pipelines, metric data from this source flows through the configured processors to all pipeline destinations. The New Relic destination reconstructs Infrastructure samples in their native format before it sends them to New Relic.
Configuration
Default protocol paths
You can change Infrastructure paths and upstream service URLs in Advanced options. A custom upstream URL overrides automatic regional routing for that service.
Configure a sender
- For an APM language agent and Telemetry SDK example, see New Relic Java app.
- For the New Relic Infrastructure agent, see New Relic Infrastructure agent.
Infrastructure authentication
The Infrastructure agent sends its New Relic license key in theX-License-Key header. Sawmills does not put the raw key in OpenTelemetry attributes.
The New Relic destination must use the same license key as the Infrastructure agent. This keeps identity, inventory, and metric data in the same New Relic account. The collector rejects Infrastructure export if the source key and destination key do not match.
Warning: Do not use a New Relic User API key. Use the same ingest license key in the Infrastructure agent and the New Relic destination.
Region routing
Sawmills selects the default New Relic service hosts from the license key region.
The source key and destination key must belong to the same account and region. If you configure a custom upstream URL, configure all related services for the same region.
Supported Infrastructure versions
The minimum supportednewrelic-infrastructure Helm chart version is 4.0.1. Sawmills validated this configuration:
Later versions are supported when they keep the same protocol paths and native sample format. Test a later version in staging before you use it in production.
Metric API format
Supported Metric API types:gaugecount, withinterval.mssummary
APM agent protocol
Supported methods:preconnectconnectmetric_data