sked logs triggered-action

Fetch execution logs for a triggered action by name.

Overview

Fetch execution logs for a triggered action by name.

A banner showing the time zone the Started and Completed columns use is printed above the table. Started shows the scheduled time for an entry that has not started yet. Completed stays blank until the entry is terminal.

Usage 

$ sked logs triggered-action --name <value> [--range <value> | --from <value> [--to <value>]] [--order <value>] [--output <value>] [--force] [--json] [--timezone <value>] [--alias <value>]

Examples 

$ sked logs triggered-action --name my-triggered-action --range last-7-days

$ sked logs triggered-action --name my-triggered-action --from 48h --to 24h

$ sked logs triggered-action --name my-triggered-action --range today --json

$ sked logs triggered-action --name my-triggered-action --range yesterday --output ./logs

Flags

Flag Description Required
--name= The name of the triggered action Yes
--range= Shorthand time range: today, yesterday, last-week, last-7-days, last-30-days No
--from= Start of the time range: ISO 8601, a duration such as 24h or 7d, or a range keyword No
--to= End of the time range: ISO 8601, a duration, or a range keyword No
--order= Sort order: asc (default) or desc No
-o, --output= Directory to write the logs to instead of printing them No
--force Overwrite an existing output file No
--timezone= IANA time zone to display times in, and to interpret --range and date-only --from/--to in; defaults to your system time zone No
-a, --alias= The alias of the Skedulo tenant to fetch logs from No

Global flags

Flag Description Required
--json Output raw JSON. Always in UTC, unaffected by --timezone. No

See also

Skedulo CLI Studio’s log viewer opens the same logs in an interactive, scrollable session.