New Relic OTel ingestion
Community-contributed integration
This integration is community-maintained. Configures via the standard OpenTelemetry path. Reference: ory/integrates/monitoring-observability/new-relic.
New Relic ingests OpenTelemetry over OTLP/HTTP. Ory products emit OTel traces and metrics that New Relic consumes directly.
Quick reference
| Setting | Value |
|---|---|
| OTLP endpoint (US) | https://otlp.nr-data.net:4318 |
| OTLP endpoint (EU) | https://otlp.eu01.nr-data.net:4318 |
| Auth | header api-key: {$NEW_RELIC_LICENSE_KEY} |
Configuration
Set the standard OTel environment variables on each Ory service:
TRACING_PROVIDER=otel
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.nr-data.net:4318
OTEL_EXPORTER_OTLP_HEADERS=api-key={$NEW_RELIC_LICENSE_KEY}
OTEL_SERVICE_NAME=ory-kratos
For production, prefer an OpenTelemetry Collector in front of New Relic for batching, retries, and sampling in one place.
Notable
- New Relic enforces attribute count and size limits. Sending
identity.traitsas a flat blob will hit them. - Use Account – Ingest scope license keys, never full user keys.
- Sample at the OTel SDK or collector level, not on the backend side.
