Export to New Relic

Scrape Baseten metrics with an OpenTelemetry Collector and send them to New Relic over OTLP.

Use an OpenTelemetry Collector distribution that includes the Prometheus receiver and OTLP/HTTP exporter, such as the contrib distribution. The receiver scrapes Baseten; the exporter sends those metrics to New Relic’s OTLP endpoint.

Create a metrics-only API key, then set these environment variables in the Collector’s runtime:

BASETEN_METRICS_API_KEY · string · required

The Baseten metrics-only API key.

NEW_RELIC_LICENSE_KEY · string · required

The ingest license key for the New Relic account that receives the metrics.

NEW_RELIC_OTLP_ENDPOINT · string · required

Your account’s regional OTLP endpoint, such as https://otlp.nr-data.net for the United States or https://otlp.eu01.nr-data.net for the European Union. The exporter appends /v1/metrics.

Configure the Collector:

config.yaml

receivers:
  # Configure a Prometheus receiver to scrape the Baseten metrics endpoint.
  prometheus:
    config:
      scrape_configs:
        - job_name: 'baseten'
          scrape_interval: 60s
          metrics_path: '/metrics'
          scheme: https
          authorization:
            type: Bearer
            credentials: ${env:BASETEN_METRICS_API_KEY}
          static_configs:
            - targets: ['app.baseten.co']
processors:
  batch:
exporters:
  # Send metrics to New Relic over OTLP/HTTP.
  otlphttp/newrelic:
    endpoint: ${env:NEW_RELIC_OTLP_ENDPOINT}
    headers:
      api-key: ${env:NEW_RELIC_LICENSE_KEY}
service:
  pipelines:
    metrics:
      receivers: [prometheus]
      processors: [batch]
      exporters: [otlphttp/newrelic]

Start the Collector with this configuration and check its logs for scrape or export errors. Use New Relic’s metrics explorer to find the exported Baseten metrics.

Keep all collectors within Baseten’s metrics rate limit. See the exported metrics reference for available measurements and New Relic’s OTLP guidance for regional endpoints, batching, and ingest limits.