Pull logs and metrics

Use the dashboard, Baseten CLI, or Management API to investigate a deployment or monitor an environment. For dashboard filtering and request correlation, see Logs. For dashboard graphs and their interpretation, see Metrics. To collect metrics continuously in an external monitoring system, use metrics export. For CLI examples, install and authenticate the Baseten CLI. For API examples, set BASETEN_API_KEY to a Baseten API key. Replace the model and deployment ID placeholders with your IDs.

Fetch and stream logs

Pull logs to debug an incident, filter for an error, or use the output in a script. Fetch a time window of up to 7 days:

UI
Baseten CLI
Management API

To view logs:

Sign in to your workspace at app.baseten.co and choose Dedicated Inference in the sidebar.
Select your model.
Choose Logs.
Open the dropdown showing the current environment or deployment, then choose your deployment under Switch deployments.

Filter by level or replica, search, or follow live output with the controls at the top of the logs view.

Fetch logs from a deployment:

baseten model deployment logs --model-id <model-id> --deployment-id <deployment-id> --since 1h

[2026-07-07 10:33:58]: Deploy was a success.
[2026-07-07 10:33:44]: (nvsmp) Completed model.load() execution in 6 ms
[2026-07-07 10:33:44]: (nvsmp) Uvicorn running on http://0.0.0.0:8080 (Press CTRL+C to quit)

The parenthesized prefix on each line is the replica that emitted it.To stream live logs, pass --tail instead of a time window:

baseten model deployment logs --model-id <model-id> --deployment-id <deployment-id> --tail

[2026-07-07 10:33:44]: (nvsmp) Completed model.load() execution in 6 ms
[2026-07-07 10:33:58]: Deploy was a success.
...

Streaming continues until the deployment leaves a runnable state or you interrupt with Ctrl-C. For machine-readable output, add --output jsonl to stream one JSON log entry per line:

baseten model deployment logs --model-id <model-id> --deployment-id <deployment-id> --tail --output jsonl

{"level":"INFO","message":"Completed model.load() execution in 6 ms","replica":"nvsmp","timestamp":"1783445624380306972"}
{"level":"INFO","message":"Deploy was a success.","replica":"","timestamp":"1783445638726940011"}
...

Narrow the stream with --jq: --jq '.message' extracts one field per line, and --jq 'select(.level=="ERROR") | .message' keeps only error lines.

Fetch logs from a deployment:

curl "https://api.baseten.co/v1/models/{model_id}/deployments/{deployment_id}/logs" \
  -H "Authorization: Bearer $BASETEN_API_KEY"

{
  "logs": [
    {
      "timestamp": "1783445638726940011",
      "message": "Deploy was a success.",
      "replica": "",
      "request_id": null,
      "level": "INFO"
    },
    {
      "timestamp": "1783445624380306972",
      "message": "Completed model.load() execution in 6 ms",
      "replica": "nvsmp",
      "request_id": null,
      "level": "INFO"
    }
  ]
}

The window defaults to the last 30 minutes; pass start_epoch_millis to widen it, up to 7 days. Timestamps are epoch nanoseconds. The API fetches fixed windows only; to follow logs live, use the CLI’s --tail.

For more information about filters like log level, search patterns, and request ID, see logs and the logs endpoint.

Fetch metrics

View or fetch a deployment’s replica count, request volume, and end-to-end latency quantiles to check its health.

UI
Baseten CLI
Management API

To view metrics:

Sign in to your workspace at app.baseten.co and choose Dedicated Inference in the sidebar.
Select your model.
Choose Metrics.
Open the dropdown showing the current environment or deployment, then choose your deployment under Switch deployments.

The metrics view charts request rates by status code, latency percentiles, and replica counts. Set the window with the time-range selector at the top.

Fetch a deployment’s current metrics:

baseten model deployment metrics --model-id <model-id> --deployment-id <deployment-id>

METRIC                                    QUANTILE  STAT  VALUE
baseten_replicas_active                                       1
baseten_end_to_end_response_time_seconds  0.5                 -
baseten_end_to_end_response_time_seconds  0.9                 -
baseten_end_to_end_response_time_seconds  0.95                -
baseten_end_to_end_response_time_seconds  0.99                -
baseten_end_to_end_response_time_seconds            avg       -

Latency values show - until the deployment has served requests in the window; once it has, a STATUS column also breaks out request counts per response code. The default is a current snapshot; pass --mode summary or --mode series with --since to aggregate over a window instead.

Fetch a deployment’s current metrics:

curl "https://api.baseten.co/v1/models/{model_id}/deployments/{deployment_id}/metrics" \
  -H "Authorization: Bearer $BASETEN_API_KEY"

{
  "start_epoch_millis": 1783445679297,
  "end_epoch_millis": 1783445679297,
  "mode": "CURRENT",
  "step_seconds": null,
  "metric_descriptors": [
    {
      "name": "baseten_replicas_active",
      "unit_hint": "COUNT",
      "kind": "GAUGE",
      "label_sets": [{}]
    }
  ],
  "metric_values": [
    {
      "start_epoch_millis": 1783445679297,
      "values": [[1.0]]
    }
  ]
}

Each metric_values entry represents a time window. Within that entry, values[i] corresponds to metric_descriptors[i]. The values in each inner array follow that descriptor’s label_sets order.

For more information about modes, windows, and metric selection, see metrics and the metrics endpoint (beta). For what each metric means, see Metrics.

Fetch environment logs and metrics

Use environment scope to follow logs and metrics across promotions. It includes the deployments serving that environment during the selected time window, so you can investigate a rollout without querying each deployment separately.

UI
Baseten CLI
Management API

To view an environment’s logs and metrics:

Sign in to your workspace at app.baseten.co and choose Dedicated Inference in the sidebar.
Select your model.
Choose Logs or Metrics.
Open the dropdown showing the current environment or deployment, then choose your environment under Switch environments.

The view includes deployments that served that environment during the selected time window.

To fetch logs, target the environment by name instead of a deployment ID:

baseten model environment logs --model-id <model-id> --environment production --since 1h

[2026-07-09 08:49:09]: (w44tt) Application shutdown complete.
[2026-07-09 08:48:41]: Scaling down replicas due to inactivity
[2026-07-09 08:34:09]: (67wjm) Terminated
...

The same windows and filters as deployment logs apply, including --tail for live streaming and --output jsonl for machine-readable output.Fetch the environment’s current metrics:

baseten model environment metrics --model-id <model-id> --environment production

METRIC                                    QUANTILE  STAT  VALUE
baseten_replicas_active                                       1
baseten_end_to_end_response_time_seconds  0.5                 -
baseten_end_to_end_response_time_seconds  0.9                 -
baseten_end_to_end_response_time_seconds  0.95                -
baseten_end_to_end_response_time_seconds  0.99                -
baseten_end_to_end_response_time_seconds            avg       -

The default is a current snapshot; pass --mode summary or --mode series with --since to aggregate over a window. In series mode the window splits at each promotion, so every point reflects the deployment serving the environment at that time.

Fetch logs from the environment:

curl "https://api.baseten.co/v1/models/{model_id}/environments/production/logs" \
  -H "Authorization: Bearer $BASETEN_API_KEY"

{
  "logs": [
    {
      "timestamp": "1783612149447676900",
      "message": "Application shutdown complete.",
      "replica": "w44tt",
      "request_id": null,
      "level": "INFO"
    }
  ]
}

Fetch the environment’s current metrics:

curl "https://api.baseten.co/v1/models/{model_id}/environments/production/metrics" \
  -H "Authorization: Bearer $BASETEN_API_KEY"

{
  "start_epoch_millis": 1783968056212,
  "end_epoch_millis": 1783968056212,
  "mode": "CURRENT",
  "step_seconds": null,
  "metric_descriptors": [
    {
      "name": "baseten_replicas_active",
      "unit_hint": "COUNT",
      "kind": "GAUGE",
      "label_sets": [{}]
    }
  ],
  "metric_values": [
    {
      "start_epoch_millis": 1783968056212,
      "values": [[1.0]]
    }
  ]
}

The logs endpoint accepts the same time windows and filters as deployment logs. The metrics endpoint accepts the same windows, modes, and metric selection as deployment metrics.

For more information, see environment logs and environment metrics, and the environment logs endpoint and environment metrics endpoint (beta).

Next steps

Check logs and metrics before and after a deployment change.

Terminate a stuck replica you found misbehaving in the logs.
Scale a deployment if metrics show sustained queueing or idle replicas.
Interpret dashboard graphs with the Metrics guide, or look up exact names, types, and labels in the exported metrics reference.

Get started

Model APIs

Inference

Training

Development

Deployment

Engines

Model Labs

Organization

Hosting options

Observability

Troubleshooting

Pull logs and metrics

Fetch and stream logs

Fetch metrics

Fetch environment logs and metrics

Next steps

​Fetch and stream logs

​Fetch metrics

​Fetch environment logs and metrics

​Next steps

Fetch and stream logs

Fetch metrics

Fetch environment logs and metrics

Next steps