Export to Datadog

Use an OpenTelemetry Collector distribution that includes the Prometheus receiver and Datadog exporter, such as the contrib distribution. The receiver scrapes Baseten; the exporter sends those metrics to your Datadog account. Create a metrics-only API key, then set these environment variables in the Collector’s runtime:

string

required

The Baseten metrics-only API key.

string

required

An API key for the Datadog account that receives the metrics.

string

required

Your Datadog site, such as datadoghq.com or datadoghq.eu.

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:
  # Configure a Datadog exporter.
  datadog:
    api:
      key: ${env:DATADOG_API_KEY}
      site: ${env:DATADOG_SITE}
service:
  pipelines:
    metrics:
      receivers: [prometheus]
      processors: [batch]
      exporters: [datadog]

Start the Collector with this configuration and check its logs for scrape or export errors. Search Datadog’s Metrics Explorer for the exported Baseten metrics. Keep all collectors within Baseten’s metrics rate limit. See the exported metrics reference for available measurements and the Datadog exporter documentation for exporter settings and batching guidance.

Get started

Model APIs

Inference

Training

Baseten Grid

Frontier Gateway

Sandboxes

Development

Deployment

Engines

Model Labs

Organization

Hosting options

Observability

Troubleshooting

Export to Datadog