orke package logs
Read output or error logs by cycle, step, and attempt.
When to use it
Read output or error logs by cycle, step, and attempt.
Usage
Syntax · [ ] marks optional arguments
orke package logs --slug <string> --cycleId <string> --step <integer> --attempt <integer> --stream <stdout|stderr> [--maxBytes <integer>]Options
| Options | Required? | Value and description |
|---|---|---|
--slug | Required | Package identifier returned by list or create. |
--cycleId | Required | Cycle ID to query, or the observed current cycle ID. |
--step | Required | Step number. Range: 1–2147483647 |
--attempt | Required | Attempt number for that step. Range: 1–2147483647 |
--stream | Required | stdout | stderrstdout contains answer output; stderr contains progress and error logs. |
--maxBytes | Optional | Byte budget for records read in one call. Range: 1–8192 |
Common management options and errors →
Example
Terminal
orke package logs --slug package_slug --cycleId observed_cycleId --step 1 --attempt 1 --stream stdoutReplace the example IDs, folders, references, and revision with values from actual queries. Element references such as e7 must also come from the latest observation.
What to check in the result
PackageLogSlice: text/startOffset/endOffset/truncated/readState
Behavior and states to watch
- Read a log tail of up to 8192 bytes once, using a fixed end position. Distinguish missing, ready, and unreadable.