bdy target exec logs

View as Markdown
$bdy target exec logs [options] <identifier> <exec-id>

Show execution logs Required scopes: TARGET_READ

ARGUMENTS
identifier
Target identifier (required)
exec-id
Execution ID (required)
OPTIONS
--context <name>
Connection and scope context: default, git, link or a saved name. Overrides the globally active context for this invocation.
--examples
Show only examples; with this flag --format accepts text, json or jsonl
--verbose
Show REST API requests, responses, timing and retries on stderr
-w, --workspace <domain>
Workspace URL handle. Can be set via variable: BUDDY_WORKSPACE
-p, --project <name>
Project name. Can be set via variable: BUDDY_PROJECT
--pipeline <identifier>
Pipeline identifier to scope the target to. Requires --project
--environment <identifier>
Environment identifier to scope the target to. Resolves a workspace environment; add --project to point at a project environment
--offset <n>
Log line offset. Default: 0
--limit <n>
Maximum number of log lines. Default: all lines
--format <text|jsonl>
Output format: jsonl, text. JSONL CLI errors: {type:"error",error:{code,message,hint}}, exit 1 (2 or 3 with --exit-code). Default: text (choices: "text", "jsonl")
--exit-code
Use semantic exit codes: 0 success, 1 unsuccessful, 2 command error, 3 not found, 8 pending
-h, --help
display help for command

Documentation for bdy v1.25.34

Last modified on Nov 3, 2026

Examples

Return the execution state using semantic exit codes
bdy target exec logs target-identifier exec-id --exit-code$
Show logs of execution
bdy tg exec logs target-identifier exec-id$
Show logs of execution starting from line 100
bdy tg exec logs target-identifier exec-id --offset 100$
Return log records as JSONL
bdy target exec logs target-identifier execution-id --format jsonl$