Set the OTLP endpoint to the New Relic OTLP endpoint (otlp.nr-data.net:4317 for gRPC or 4318 for HTTP) in the SDK or Collector exporter config
Add the New Relic license key as a header: api-key: <LICENSE_KEY> in the OTLP exporter headers configuration
Set the service.name resource attribute in the SDK or via OTEL_RESOURCE_ATTRIBUTES=service.name=my-service for correct entity synthesis in New Relic
Verify entity creation under APM & Services > Services - OpenTelemetry in the New Relic UI and confirm that traces, metrics, and logs are linked under the entity
If using the OTel Collector as a gateway, configure the New Relic exporter (otlphttp exporter) with compression: gzip to reduce egress bandwidth
Known gotchas
New Relic requires the service.name resource attribute for entity synthesis; services missing this attribute appear under an Unknown Service umbrella and are hard to find
EU region accounts must use the EU OTLP endpoint (otlp.eu01.nr-data.net); using the US endpoint causes rejected payloads with authorization errors
New Relic's OTLP ingest applies rate limits per account; bulk replay of historical data via OTLP can hit these limits and requires back-off or a support-raised quota increase
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp