Skip to main content
GET
Requires version 1.1.9 or later of the Archetype platform.
Starting with version 2.0.1, this endpoint is removed from the platform. Run packages through deployments and sessions instead: deploy a package with Create Deployment, then open a session on it with Create Session. To move existing code, see Migrating from Bundles and Instances.

Overview

This endpoint returns a page of run log entries, newest first. Log lines come from the executor (JOS job events) rather than from the agent event log, so they carry the executor’s own severity vocabulary and event kinds. The list is empty for a no-op run. Filter by severity, or search the message and event type. For a run started with mode: serving, the lines come from the worker that hosts the agent instead. They start while the run is still deploying, so you can follow its model downloads, loads and warm-ups as they happen. v2.0.1+

Request

string
required
Agent agt_ id.
integer
default:"100"
Page size. Minimum 1, maximum 1000.
string
Forward cursor: return log lines older than this page. Pass the previous page’s next_cursor. Opaque — not a log id; never compute on it. Mutually exclusive with before.
string
Backward cursor: return log lines newer than this page. Opaque, as after is. Mutually exclusive with after.
string
Filter to a single severity. Omit for all severities. One of INFO, WARN, ERROR, SUCCESS, FAILED — any case is accepted, and warning is accepted for warn.
Starting with version 2.0.1, a serving run’s log contains only INFO, WARN and ERROR lines. Filtering a serving run by SUCCESS or FAILED returns an empty page; read the run’s outcome from its status instead.
Case-insensitive substring match over the line’s message and event type. Omit for no search filter.

Response

array
required
The page, newest first. Each entry is a log line.
boolean
required
True when more log lines exist beyond this page in the direction of travel.
string
Cursor for the next page in the same direction — pass it as after when paging forward, or as before when you supplied before. null when has_more is false.
string
Cursor to step back the way this page was reached — pass it as before after a forward page, or as after after a backward one. null when the request carried no cursor. v1.1.11+

Log entry object

One executor-sourced log line for a run: a JOS job event for a batch run, or a line from the hosting worker for a serving run.
string
required
Executor-assigned log id. Stable, but not this list’s cursor.
string
required
Severity of the line, in the executor’s vocabulary: INFO, WARN, ERROR, SUCCESS, or FAILED.
string
required
Executor’s event kind, e.g. status_change. A line reported by a node of the agent’s graph uses {node}.{stage}: {node}.loading while its models load, {node}.running after.
string
required
When the line was logged (date-time).
string
The log message; null when the event carries none.
integer
Index of the worker that logged the line, when it came from one.

Important Notes

  • The cursor here is opaque and is not a log id. Pass next_cursor back verbatim; never derive it from data[last].id or compute on it.
  • after and before are mutually exclusive — send at most one of them.
  • level uses the executor’s vocabulary, which includes SUCCESS and FAILED — these have no equivalent in the agent event log’s three levels.
  • A no-op run produces no executor logs, so data comes back empty.
  • A serving run’s log holds only its recent lines, not its whole history. The oldest lines drop out of a long-running agent’s log, and the log comes back empty once no worker hosts the run. Debug lines are never returned. v2.0.1+
  • While a serving run downloads, loads or warms up a model, it logs Still <step> after <elapsed> once a minute. This lets you tell a slow load from a stuck one. v2.0.1+
  • A 503 means the worker hosting a serving run could not be read at that moment. Retry the request. v2.0.1+