Skip to content
downpipes docs

Send downpipes backup-health metrics to New Relic

New Relic can take a direct OTLP metrics push from downpipes to your New Relic OTLP endpoint. One honest caveat comes first. New Relic’s own documentation describes OTLP protobuf and does not confirm the OTLP/HTTP JSON encoding this engine sends, and New Relic offers no hosted agentless pull. So configure the push, then verify New Relic actually ingested it against a live account before you rely on it.

Do not assume the push works from a 2xx on the delivery trail alone. Confirm the metrics themselves arrived in your account, and if they did not, use the /metrics scrape route instead.

What you need

  • A New Relic ingest key (New Relic’s licence key) and your region’s OTLP metrics endpoint.
  • Owner access to the downpipes console to set the OTLP metrics push.

Set it up

  1. In New Relic, get an ingest key and note your region’s OTLP metrics endpoint: US is https://otlp.nr-data.net/v1/metrics, and EU is https://otlp.eu01.nr-data.net/v1/metrics.
  2. In the console, open Integrations, choose the New Relic tile, and set up the OTLP metrics push there.
  3. Set the Endpoint URL to your New Relic OTLP metrics URL, the auth header name to api-key, and the auth header value to your ingest key.
  4. Enable the destination. There is no test send, so wait for the delivery trail after the next scheduler tick.
  5. Verify the data actually landed by querying your account for the downpipe_* metrics. If they do not appear, New Relic has not accepted the JSON body, so switch to the scrape route: New Relic’s Prometheus remote-write integration, or its infrastructure agent’s Prometheus config, pointed at a minted metrics token.
  6. If you use that scrape route and Cloudflare Access fronts your console hostname, an unattended scrape is turned away at the edge before the engine ever sees the bearer, whatever credential it carries. Carve a path-scoped Access exemption over /metrics before pointing the remote-write integration or infrastructure agent at it. The full remedy is on the /metrics endpoint.

Good to know

  • New Relic’s documentation confirms OTLP protobuf but not OTLP/HTTP JSON, which is what this engine sends, so treat the direct push as unverified until you have seen the metrics land in your own account. This page does not claim the push works; it says to test it first.
  • New Relic has no hosted agentless scraper, so the pull alternative still means running the remote-write integration or the infrastructure agent yourself against a minted metrics token. The push mechanics and the per-vendor OTLP-acceptance table are on OTLP metrics push, and the scrape route is on the /metrics endpoint.

Last updated .