Services

LogService

plany.gamelog.v1.LogService — reading what a game server or sandbox printed.

Endpoint api.plany.cloud:443 · Guide · Reference

Everything a game server writes to stdout or stderr is kept, with Plany's own notes on installing, launching and stopping it alongside. There is nothing to set up: a server's output is collected from its first start.

Two calls read it back:

Call	What it returns
`ListLogLines`	Lines from one game server or sandbox, newest first. Pass `order: ORDER_OLDEST_FIRST` to read forwards, `contains` to search, `time_range` for a window.
`ListAgentRuns`	Each start of the server that produced lines. Pass one's id as `agent_run_id` to read a single run.

Servers → choose a server → Logs

Each record carries the line's text, the stream it came from (STDOUT, STDERR, or AGENT for Plany's own notes), when the server printed it, and a sequence number. Sequence numbers restart with each run, so order lines across a restart by run first.

Gaps

When a server produces lines faster than they can be kept, some are dropped rather than slowing the game down, and the response says so in gaps.

A gap is invisible in the lines around it. If you show logs to somebody, show the gaps too, rather than presenting the surrounding lines as complete.

Permissions

Reading logs needs gamelog.logs.list, checked on the server you name, so you can read the logs of exactly the servers you hold a role on. A game server can write its own log and cannot read it back. See Logs.