Skip to main content

New Relic

Overview​

New Relic sends logs, metrics, and traces to New Relic using the OpenTelemetry Protocol (OTLP). The Praxis New Relic destination is a catalog node for the same OTLP-based export path as the generic OTLP destination.

Supported types: Logs · Metrics · Traces

Configuration​

All destination fields match the OTLP reference: protocol, endpoints, TLS, headers, queues, retries, and authentication. See OTLP destination for the full parameter list and examples.

Notes for New Relic​

  • Use the OTLP hostname and path from your New Relic account’s OpenTelemetry / ingest settings (gRPC and HTTP differ; pick protocol and endpoints accordingly in Praxis).
  • New Relic typically expects the api-key header (or the header name shown in the New Relic UI) on OTLP requests, with your license key or ingest key as the value. Set this under HTTP headers or gRPC headers in the destination, or use a supported credential type if you centralize that secret.
  • Follow New Relic’s guidance on which signals (logs, metrics, traces) are enabled for your account and which OTLP version they support.

External documentation​