Get Agent Logs
Tailed [AGENT]-prefixed Flink TM logs + recent job exceptions.
The write:agents gate is intentional: agent log lines may contain
customer payloads that flowed through prompts and tool args. Tightening
the audit surface here mirrors how the Streamkap MCP project key blob
is gated.
Per-line scoping is namespace-wide for now - when multiple agents share a TaskManager, lines from other agents may appear. Documented limitation until the Java runtime emits per-line agent IDs.
since is an optional ISO 8601 cutoff for incremental polling on the
unified observability surface. The underlying tail window is Nx4 the
requested tail count; if since is far enough back that the
window doesn’t reach it, the response is still bounded by tail (the
caller can widen tail to compensate).
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Query Parameters
Response
Successful Response
Combined response for GET /agents/{id}/logs.
lines are tailed and parsed agent log lines from the Flink TaskManager
pods in the tenant's namespace; see :class:FlinkClusterClient.get_taskmanager_logs
for per-line scoping caveats. flink_exceptions are pulled from the
Flink REST /jobs/{jid}/exceptions endpoint when the job is live.
Per-line scoping of returned lines. namespace means lines may include [AGENT] entries from other agents sharing a TaskManager (current limitation). agent will be returned once the Java runtime emits per-line agent IDs.
namespace, agent