get_log_lines

Read every log line the service wrote under one trace id, in order.

Logread-onlyidempotentMCP tool

A trace id covers one request end to end or one pass of a background loop; the service answers it on any call that failed, and it is on every line in the log. This is how to find out what happened behind a failure, on whichever engine the call was made to.

Calling it#

curl -X POST http://127.0.0.1:8787/log.v1.LogService/GetLogLines \
  -H 'Content-Type: application/json' \
  -d '{
  "traceId": "<traceId>"
}'

komrad rpc get-log-lines \
  --trace-id <string>

{
  "name": "get_log_lines",
  "arguments": {
    "traceId": "<traceId>"
  }
}

Offered by the komrad MCP server to orchestrator agents.

Request#

GetLogLinesRequest#

Field Type Description

Field	Type	Description
`traceId`	string	The trace id a failed call answered with, or one list_recent_traces listed. required, at most 128 characters

traceId

string

The trace id a failed call answered with, or one list_recent_traces listed.

required, at most 128 characters

Response#

GetLogLinesResponse#

Field	Type	Description
`lines`	list of LogLine	Every line written under the trace id, in the order the log holds them.

Types#

LogLine#

Field	Type	Description
`time`	string	When the line was written, in RFC 3339.
`level`	string	The severity as the log spells it, such as INFO or ERROR.
`message`	string	What the line says.
`fields`	json	Everything else the line carried, keyed as the log keys it.