v1

latestOpenAPI 3.1.02026-07-134612587.0 KB

Endpoints

Get endpoint logs (structured, paginated) [READ]

Cursor-based pagination split into two concerns:

Time window (since / until, RFC 3339, inclusive): immutable filter carried across all paginated requests for a given view.
Cursor (after / before): opaque pagination cursor produced by the API in the Link header. Clients MUST treat it as opaque.

order controls which side of the window limit cuts from (desc keeps the newest, asc keeps the oldest). Response entries are always returned in chronological (ascending) order regardless of order.

All log entries sharing a boundary millisecond are always included, even if that exceeds limit.

Always returns application/json. For a kubectl-style line-per-log rendering, use /v3/endpoint/{namespace}/{name}/logs/download.

get/v3/endpoint/{namespace}/{name}/logs

Path parameters

namespacestring required

User or organization name

namestring required

Endpoint name

Query parameters

replicastring

Replica ID

levelstring

Filter by log level

searchstring

Case-insensitive substring search on log line

sincestring

Time window lower bound, inclusive (RFC 3339)

untilstring

Time window upper bound, inclusive (RFC 3339)

afterstring

Opaque pagination cursor (from Link header). Do not construct.

beforestring

Opaque pagination cursor (from Link header). Do not construct.

orderstring

Sort direction: asc or desc (default desc — keep newest of the window)

limitinteger

Max lines to return (default 1000, max 5000)

line_max_lengthinteger

Max line length

Response

Log entries returned successfully. Link header contains rel=next, rel=prev and rel=next_sse cursors.