Retrieve build logs¶

Every image build produces builder output—base image pulls, dependency resolution, each Dockerfile step, and the error that stopped it if it failed. Build logs are how you find out why a build reported FAILED, and how you watch a long build make progress.

The builder exports its output as OpenTelemetry logs, and you read them from the platform observability surface, keyed by artifact:

GET /api/v2/otel/artifact/{artifactId}/logs/

Note the singular artifact in the path—that segment is the OTel entity type, not the Workload API's /artifacts collection. The Workload API itself does not expose or proxy /otel/* routes.

Build logs cover the build. For logs from the container once it is running, see Monitor telemetry and health.

Retrieve a build log¶

Retrieve build output directly through the REST API, or with the CLI when the project directory is already linked.

# Every build the artifact has ever run
curl -s "${DATAROBOT_ENDPOINT}/otel/artifact/${ARTIFACT_ID}/logs/" \
  -H "Authorization: Bearer ${DATAROBOT_API_TOKEN}"

# One build, filtered by its Workload API build ID
curl -s "${DATAROBOT_ENDPOINT}/otel/artifact/${ARTIFACT_ID}/logs/?searchKeys=external_build_id&searchValues=${BUILD_ID}" \
  -H "Authorization: Bearer ${DATAROBOT_API_TOKEN}"

dr artifact build logs ${ARTIFACT_ID} ${BUILD_ID}

# Show warnings and errors only
dr artifact build logs ${ARTIFACT_ID} ${BUILD_ID} --level warn

The stream is scoped to the artifact, so without a filter it contains every build the artifact has run. external_build_id narrows it to one build:

The response is JSON, one object per log record:

{
  "count": 100,
  "next": "https://app.datarobot.com/api/v2/otel/artifact/68f0.../logs/?offset=100&limit=100",
  "previous": null,
  "data": [
    {
      "timestamp": "2026-08-18 09:14:22.481000+00:00",
      "level": "INFO",
      "message": "Step 6/12 : RUN uv sync --frozen"
    }
  ]
}

stacktrace, spanId, and traceId appear on records that carry them. count is the size of the page you were served, not the total number of records—page through with next until it is null.

Query parameters¶

The following table describes each supported parameter.

while true; do
  clear
  curl -s "${DATAROBOT_ENDPOINT}/otel/artifact/${ARTIFACT_ID}/logs/?searchKeys=external_build_id&searchValues=${BUILD_ID}" \
    -H "Authorization: Bearer ${DATAROBOT_API_TOKEN}" \
    | jq -r '.data[] | "\(.timestamp) \(.level) \(.message)"'
  sleep 10
done

When logs are not available¶

An artifact with no matching records returns 200 with an empty data array rather than an error, so an empty result is not a failure:

Error responses:

Diagnose a failed build¶

Read the log from the bottom: the last builder step before the error is nearly always the cause.

If a build succeeds but the container does not start, the problem is runtime rather than build: check the entrypoint, the port, and the readiness probe against Container requirements, then use Health and readiness.

Next steps¶

Reading build output is one part of managing the build lifecycle; the following resources cover the surrounding build operations and Dockerfile configuration.