jobs:events
rai jobs:events [OPTIONS]Get events for a job.
Events have no human table form. Output is machine-readable:
- Default table mode still prints the historical raw JSON events object,
{"events": [...], "continuation_token": ...}. This matches the historical pre-1.0 shape, so scripts that consume the default form continue to work unchanged. --json/--output jsonwraps that object under ajob_eventskey,{"job_events": {"events": [...], "continuation_token": ...}}, to match the wrapper-key shape used by the rest of the CLI under machine-readable output modes (e.g.{"jobs": [...]}fromjobs list).--output yamluses the samejob_eventswrapper and emits YAML.
Use --output json or --output yaml when piping into a tool that
expects the consistent wrapped shape; otherwise the unwrapped default
JSON form is fine.
Options
Section titled “Options”| Option | Type | Description |
|---|---|---|
--type | text | Job type (Logic/Prescriptive/Predictive). Required. Default: Sentinel.UNSET. |
--id | text | Job id. Required. Default: Sentinel.UNSET. |
--continuation-token | text | Continuation token from a previous events call (optional). Default: “. |
--stream-name | text | Events stream name (optional). Defaults to profiler for Direct Access Logic jobs and progress otherwise. |