Skip to main content
Baseten exposes deployment metrics in Prometheus format at https://app.baseten.co/metrics. Scrape this endpoint to monitor your models in Prometheus, Grafana Cloud, Datadog, New Relic, or another Prometheus-compatible system.

Create a metrics API key

Create a workspace API key for your collector. This key can export metrics but can’t deploy or invoke models.
Sign in to the Baseten CLI:
The CLI stores your login in a local profile. This profile authenticates Baseten CLI commands, but it doesn’t provide credentials to curl, Prometheus, or another collector.Create the metrics key:
To restrict the key to specific models, repeat --model-id for each model:
The CLI prints the key once:
Store the new key in your collector’s secret store. Don’t use a developer’s personal CLI credential for a shared or production collector.

Choose an integration

Scrape the endpoint once per minute. Baseten collects workload metrics every 30 seconds, so a shorter interval increases request volume without providing fresher data. Use one of the following integration guides:
  • Prometheus scrapes the endpoint directly.
  • Grafana Cloud connects to the endpoint as a hosted scrape job.
  • Datadog receives the metrics through an OpenTelemetry Collector.
  • New Relic receives the metrics through an OpenTelemetry Collector.
For metric names, types, and labels, see Supported metrics. To export application-defined metrics, see Export custom metrics. You can expose a Prometheus endpoint from a custom server or push metrics directly to an upstream provider with OpenTelemetry.

Rate limit

The metrics endpoint accepts six requests per minute per organization. The limit applies across API keys and collectors in the organization. Requests above the limit return HTTP 429 Too Many Requests. Use a 60-second scrape interval for each collector. If you run multiple collectors, keep their combined request rate below six requests per minute.