sked logs export

Batch export logs for all artifacts of a given type.

Overview

Batch export logs for all artifacts of a given type. Writes one file per artifact to the output directory, splitting a file automatically once it reaches 1 GB.

Shows a confirmation table of the artifacts to export before proceeding; use --yes to skip it in scripts. A matching export-summary_<timestamp>.json file is written alongside the exported files, with per-artifact results.

Usage 

$ sked logs export --artifact <value> --output <value> [--range <value> | --from <value> [--to <value>]] [--timezone <value>] [--order <value>] [--filterByStatus <value>] [--filterByName <value>] [--force] [--yes] [--alias <value>]

Examples 

$ sked logs export --artifact triggered-action --output ./export --range last-7-days

$ sked logs export --artifact webhook --output ./export --filterByName foo,bar --yes

$ sked logs export --artifact triggered-action --output ./export --filterByStatus enabled --force

Flags

Flag Description Required
--artifact= Artifact type: triggered-action, webhook, or function Yes
-o, --output= Output directory. Filenames are generated automatically and cannot be overridden Yes
--range= Shorthand time range No
--from= Start of the time range No
--to= End of the time range No
--timezone= IANA time zone to interpret --range, --from, and --to in; defaults to your system time zone No
--order= Sort order: asc (default) or desc No
--filterByStatus= enabled or disabled. Triggered actions only No
--filterByName= Comma-separated list of artifact names to include No
--force Overwrite a file on a name collision No
-y, --yes Skip the confirmation prompt No
-a, --alias= The alias of the Skedulo tenant to export logs from No

Exits with code 1 if any individual artifact export fails; partial results are still written.