Skip to main content

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. Self-hosted Ory products (Ory Kratos, Ory Hydra, Ory Keto, Ory Oathkeeper) emit OTel traces that New Relic consumes directly. Metrics come from each service's Prometheus endpoint rather than over OTLP — scrape them with New Relic's Prometheus integration.

Self-hosted only

Ory Network does not export telemetry to customer-owned collectors — managed project configuration excludes operational settings such as tracing and logging.

Quick reference​

SettingValue
OTLP endpoint (US)https://otlp.nr-data.net:4318
OTLP endpoint (EU)https://otlp.eu01.nr-data.net:4318
Authheader 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.traits as 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.

Resources​