Skip to main content
On this page

Kater CLI Logs and bugs logs

kater logs job

Shows one job run's result: its state and times, and what the sync or the test run answered.

Use it to find out why a run failed.

Examples

Terminal window
# Find the id of the last sync_snowflake run
kater job history --kater-root . --deployment production --job sync_snowflake --limit 1
# Show that run's result, by its id
kater logs job 0f3c9a6e2b8d4f17a5c1e9b04d72a6c3 --kater-root . --deployment production

Arguments

ArgumentDescription
<run-id>The run, by the id that kater job history gives.

Options

OptionDescription
--deployment <name>Required. The deployment the run belongs to, such as production. A run of another deployment is not found.

It also takes the global options --json, --kater-root, --scope and --help.

What the result holds

result holds the answer of kater sync or kater test, with its diagnostics. A run that did not do its work gives a code in place of the answer, such as job_changed or worker_interrupted. A credential that needs a browser sign-in gives the diagnostic interactive_credentials.

See also