New Relic published a number of exporters that are used to send OpenTelemetry data over New Relic's proprietary protocol. These exporters are being deprecated in favor of sending data to New Relic using the OpenTelemetry protocol.
The exporters are listed here for reference. To migrate off these exporters, follow our quick start guide.
As mentioned above, our language-specific exporters are being deprecated. These exporters allowed applications to export OpenTelemetry data directly to New Relic. The New Relic OTLP endpoint makes this strategy obsolete since it allows applications to export data to New Relic's proprietary endpoints.
The exporters and their maintenance status are as follows:
If you deployed your own collector with a New Relic exporter, we'll continue to support this exporter at least until the native OTLP ingest is beyond pre-release. We encourage you to migrate to the OTLP exporter in your collector. If you need help with that see our quick start guide.
If you still need information about the New Relic Exporter, see the opentelemetry-collector-contrib repository.
The OpenTelemetry Collector with New Relic Exporter example demonstrates what such a setup might look like.
You can change the New Relic endpoints where you send your data.
By default, New Relic OpenTelemetry exporters send data to these US data centers:
- Spans: https://trace-api.newrelic.com/trace/v1
- Metrics: https://metric-api.newrelic.com/metric/v1
- Logs: https://log-api.newrelic.com/log/v1
You may need to override these default endpoints to send data to the EU region or to use Infinite Tracing.
To send telemetry data to New Relic’s endpoints in the EU region, use the following:
These URLs don't apply to Infinite Tracing.