Get App Logs
GET /apps/{app_id}/logs
What the running app is printing.
The app’s own pods only. The per-app egress proxy runs in the same namespace and is deliberately excluded: it is platform infrastructure that happens to live inside a tenant boundary, and its output is graph8’s, not the builder’s.
Empty until a deployment reaches deployed. The app Deployment ships with
replicas: 0 and a pause image, so a namespace that exists still has no app
pod to read until a build has been promoted.
Authorizations
Parameters
Path Parameters
Query Parameters
Lines per replica, newest last.
Lines per replica, newest last.
Header Parameters
Responses
200
Successful Response
object
Logs for one app or one of its builds.
redacted is always true and means only that graph8’s credential patterns
were applied. It is NOT a claim the output is safe to publish: these are a
customer’s own build and application logs, and an application can print a
secret in a shape no pattern matches.
object
One container’s tail of output.
A build is five steps in one pod (fetch, scan-source, build, scan-image,
push), so a single flat blob would leave a caller unable to say which step
failed. kind separates the four init steps from the one container, which
is the ordering Kubernetes actually runs them in.
object
The tail hit the per-container byte cap. Earlier output exists and was not returned.
The app’s own Kubernetes namespace. Derived from the app id, never supplied.
Lines requested per container, after clamping to the server maximum.
422
Validation Error