Skip to Content
ObservabilityNew Relic Setup

New Relic Setup

This walkthrough sets up an OTLP export from Zeotap to New Relic, so your pipeline metrics, logs, and traces appear in New Relic alongside the rest of your telemetry.

New Relic natively ingests OpenTelemetry data, so no additional collector is required — Zeotap sends directly to New Relic’s OTLP endpoint.

Prerequisites

  • A New Relic account
  • A New Relic license key (an ingest key, not a user key)
  • Whether your account is on New Relic’s US or EU data center
  • The observability.write permission in your Zeotap workspace

Step 1 — Get Your New Relic License Key

  1. In New Relic, open your account’s API keys page.
  2. Locate or create a key of type INGEST - LICENSE.
  3. Copy the key. You will paste it into Zeotap in Step 3.

Step 2 — Start a New Export in Zeotap

  1. In Zeotap, navigate to Settings → Observability.
  2. Start a new export.
  3. For the preset, choose New Relic (US) or New Relic (EU) to match your New Relic account’s data center. The endpoint and transport protocol are filled in for you.

Step 3 — Enter Your License Key

  1. Paste the New Relic license key from Step 1 into the API key field.
  2. This value is stored securely and is never shown again. If you edit the export later, leave this field blank to keep the stored key.

Step 4 — Choose Signals

Leave all three signals — metrics, logs, and traces — selected to get the full picture:

  • Metrics — run completed and failed counts, run duration, rows processed, delivery failures, and contract violations
  • Logs — a log record for each failure
  • Traces — a span for each run

Step 5 — Test the Connection

Use Test to confirm Zeotap can reach New Relic with your license key. A successful test means the endpoint and key are correct. If the test fails, re-check that the key is an ingest / license key and that the preset matches your account’s data center (US vs EU).

Step 6 — Save and Verify in New Relic

  1. Save the export. It becomes Active once enabled.
  2. In New Relic, open your telemetry data (for example, the metrics explorer or logs view).
  3. Filter by the Zeotap workspace identifier that tags all exported telemetry.
  4. Trigger a run in Zeotap (a sync, journey, or loader) and confirm the corresponding metric, and — if it failed — the log record, appears in New Relic.

Troubleshooting

SymptomLikely cause
Connection test failsWrong key type (must be an ingest/license key) or wrong data center preset (US vs EU)
No data in New RelicExport not enabled, or you are filtering on the wrong workspace tag
Export shows an error statusOpen the export to read the error detail, then correct the endpoint or key

Next Steps

Last updated on
External Export (OTLP)Overview