Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.baseten.co/llms.txt

Use this file to discover all available pages before exploring further.

truss model-logs [OPTIONS]
Fetches logs for a deployed model. Use this command to debug issues or monitor model behavior in production.

​
Options

}
​
--remote
TEXT
Name of the remote in .trussrc.
​
--model-id
TEXT
ID of the model.
​
--deployment-id
TEXT
ID of the deployment.
​
--tail
Tail for ongoing logs. Streams new log entries as they arrive.
​
--log
humanfriendly | W | WARNING | I | INFO | D | DEBUG
default:"humanfriendly"
Logging verbosity. humanfriendly (default) is pretty-printed; INFO, DEBUG, WARNING produce structured logs.
​
--non-interactive
Disable interactive prompts. Use in CI/automated contexts where stdin isn’t a TTY.
Example: Fetch logs for a specific deployment: 
truss model-logs --model-id YOUR_MODEL_ID --deployment-id YOUR_DEPLOYMENT_ID
Stream logs in real-time: 
truss model-logs --model-id YOUR_MODEL_ID --deployment-id YOUR_DEPLOYMENT_ID --tail

​
Rate limits

Baseten limits the deployment logs endpoint (POST /v1/models/{model_id}/deployments/{deployment_id}/logs) to 30 requests/second per API key. Interactive use, including --tail, stays well under that limit. Scripts that wrap truss model-logs in a tight poll loop can hit the limit and receive 429 Too Many Requests. Wait for the response’s retry_after value (in seconds) before retrying. For the full response shape and a retry example, see management API rate limits.