Configure the New Relic OTel integration to ingest OTLP data and map it to New Relic entities with correct service naming

domain: docs.newrelic.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. 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
  2. Add the New Relic license key as a header: api-key: <LICENSE_KEY> in the OTLP exporter headers configuration
  3. 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
  4. 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
  5. If using the OTel Collector as a gateway, configure the New Relic exporter (otlphttp exporter) with compression: gzip to reduce egress bandwidth

Known gotchas

Related routes

Configure an application or Collector to send OTLP telemetry to New Relic within its ingest limits
docs.newrelic.com · 6 steps · unrated
Configure Prometheus OTLP ingestion endpoint to receive metrics from OTel SDK applications directly without a Collector
prometheus.io · 5 steps · unrated
Attach OTel SDK baggage to carry tenant and request metadata across service calls without modifying span attributes
opentelemetry.io · 5 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans