dt log events
Overview
Read platform lifecycle events for a job you can read: the latest run's by default, a run's with -i, or with --job-level the job's own, such as its image builds per version, which is also what a job with no run yet shows (a job whose first build failed, for example). Admins can pass --all to search those events across jobs, including names that were never created; with --all, -e narrows the search to one or more comma-separated environments, system meaning events about no job. --resource matches substrings, case-insensitively, unless --match exact is given. Raw service logs are not returned; they stay in OpenObserve. Follow a trace with --trace-id: a user request's from the traceresponse header, a run's from its scheduler.run_created event; use dt log audit -T --with-events to include the audit row in the same call. Timestamps in text output are UTC.
Synopsis
dt log events [OPTIONS] [<process_name>]
Options
-
-a,--all
Admin-only: search lifecycle events across jobs, including names that were never created -
-A,--event=<event>
Filter by lifecycle event name, for example scheduler.placement_blocked; with --job-level also an audit action, for example job.save -
-r,--resource=<resource>
Filter by job name, run name, parent run name, workflow name, or task name (substring, case-insensitive; see --match) -
-m,--match=<match>
How --resource is compared: contains (default) or exact -
-O,--outcome=<outcome>
Filter by event outcome, one or more comma-separated: success, blocked, or failed; with --job-level also denied for the audit rows -
-v,--service=<service>
Filter by service name or event component -
-L,--severity=<severity>
Filter by log severity -
-T,--trace-id=<trace-id>
Filter by trace id: the full 32-hex id, or at least its first 8 hex characters; a run's trace id is on its scheduler.run_created event -
-i,--run-id=<run-id>
Id of the job run (latest by default; a job with no run yet shows the job-level view) -
--job-level
What the platform did to the job itself rather than to a run: its image builds per version and its schedule registration. Scans up to 31 days -
-e,--environment=<environment>
Environment of the job (dev by default). With --all: one or more comma-separated environments to search (dev, pre, prod, or system for events about no job); every environment when omitted -
-c,--child-num=<child-num>
Number of child if this is a batch job (mother-job by default) -
-S,--starttime=<starttime>
Query start time (microseconds since epoch or YYYY-MM-DDTHH:MM:SSZ). Defaults to the run window, 31 days with --job-level, or 24 hours with --all -
-E,--endtime=<endtime>
Query end time (microseconds since epoch or YYYY-MM-DDTHH:MM:SSZ); defaults to now, or to the run's end for a run, which it caps -
-o,--offset=<offset>
Skip first offset rows (default 0) -
-b,--batch-size=<batch-size>
Retrieve up to batch-size results (default 100, max 1000) -
--group-rows-only
Run view: the run's own rows and its group rows, without the rows of each child -
--children-of=<children-of>
The child rows behind one group row, by its event name (with --reason and --group), narrowed by the other filters; newest first, paged by --batch-size and --offset. With --all, --parent-run is required -
--parent-run=<parent-run>
With --children-of: the run name of the group; the run shown by default, required with --all -
--reason=<reason>
With --children-of: the reason of the group row -
--group=<group>
With --children-of: the group_id of the group row, so only the rows of that emission are listed; the event, parent run and reason repeat across scheduling passes and nodes -
-j,--json
Display results in json -
-p,--pretty
Pretty print results
Arguments
process_name(optional)
Type:String
Name of the job. Required unless --all.
Examples
Show why a job run did not start
dt log events pricing
Platform events for a specific run
dt log events -e prod -i 4711 pricing
Did the image build, and why did it fail
dt log events --job-level pricing
Admin: search lifecycle events around a name that may never have been created
dt log events --all -r pricing -O blocked,failed
Admin: events of one workflow task, by its task name
dt log events --all -r downstream_2 --match exact
Admin: every run the scheduler could not place, in prod only
dt log events --all -A scheduler.placement_blocked -e prod
Admin: follow a request's platform work
dt log events --all -T 4bf92f35
SEE ALSO
← Back to dt log