Vue Storefront is now Alokai! Learn More
New Relic exporter

New Relic exporter

New Relic receives both traces and metrics from the Alokai collector. Traces appear in APM & Services → Distributed Tracing; metrics appear in Query Your Data and can be used in dashboards and alerts.

What you need

  • License key — see Creating a license key below.
  • OTLP endpoint — the regional endpoint for your New Relic account:
    RegionEndpoint
    UShttps://otlp.nr-data.net:4317
    EUhttps://otlp.eu01.nr-data.net:4317

Creating a license key

New Relic uses Ingest - License keys for all telemetry ingestion, including OTLP. This key type has no additional scope configuration — it covers all ingest signals.

  1. Go to one.newrelic.com/api-keys.
  2. Click Create a key.
  3. Set Key type to Ingest - License.
  4. Enter a name — e.g. alokai-cloud-otel.
  5. Click Save.
  6. Copy the key — it is a 40-character hex string.

The license key is tied to a specific New Relic account. Make sure you create it in the account where you want the data to appear.

Configuring in the Console

In the Console, navigate to your instance's observability settings and enable the New Relic integration. You will be asked to provide:

  1. License key
  2. OTLP endpoint (select the one matching your account region)
  3. Which signals to enable: Traces, Metrics, or both

The collector is deployed automatically once you save.

Finding your data in New Relic

Traces appear in APM & Services if service.name is set on your application. Navigate to the service and open Distributed Tracing to explore individual traces and their spans.

Metrics can be queried using NRQL in Query Your Data. Custom metrics emitted by your application are available under their original names as defined in your OTel instrumentation.

Service naming

New Relic uses the service.name OTel resource attribute to group traces into services. Set it via environment variables on your application:

OTEL_SERVICE_NAME=storefront
OTEL_RESOURCE_ATTRIBUTES=deployment.environment=production,service.version=1.4.2

Without service.name, traces are grouped under a generic unknown_service entry, making them difficult to locate.

Reference