App Logs

Get Deployment Logs

Why a build failed.

Returns every step of the build pod in the order Kubernetes runs them -- fetch, scan-source, build, scan-image, then push -- because "which step" is most of the answer. A step that has not started is omitted rather than returned empty, so a build in progress reports what exists so far.

An empty containers list means the build pod is gone or was never created. Build pods are reaped an hour after they finish (ttlSecondsAfterFinished), so logs for an older deployment are genuinely unavailable rather than hidden; last_error_sanitized on the deployment is what survives.

redacted is always true and means graph8's credential patterns were applied. It is NOT a claim the output is safe to publish: this is a customer's own build output and it can print a secret in a shape no pattern matches.

get/apps/{app_id}/deployments/{deployment_id}/logs

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/apps/{app_id}/deployments/{deployment_id}/logs
  • Auth: HTTP bearer

Path parameters

app_idstring required
deployment_idstring required

Query parameters

tail_linesinteger

Lines per build step, newest last.

Headers

Authorizationstring nullable
X-Org-Idstring nullable

Response

Successful Response

Changes

No recorded changes to this operation across all 2 revisions of this API.