Skip to main content
DocumentationLibraryReference
On this page

Kater CLI Logs and bugs logs

kater logs show

Shows the events that Kater logged for you.

Use it to find out why a command, a run or a compile failed. Each event gives its time, its level, where it came from and its message.

Examples

Terminal window
# Show the newest events that Kater logged for you
kater logs show
# Show only the errors from the last 2 hours
kater logs show --level error --since 2h
# Show the events of one request, by the request id that its error gave you
kater logs show --request-id 4bf92f3577b34da6a3ce929d0e0e4736
# Show the events about one saved query
kater logs show --path connections/snowflake_prod_connection/workspaces/ad_reporting/query_contracts/spend_by_platform.sql
# Keep printing new events as they come
kater logs show --follow

Options

OptionDescription
--level <level>Shows only the events at this level or above: debug, info, warn or error. The default is info.
--search <text>Shows only the events that contain this text in their source, level, message or detail. Upper and lower case match.
--since <time>Shows only the events from this time on. Give a time, such as 2026-10-12T09:00:00Z, or a time back from now, such as 15m, 2h or 1d.
--path <file>Shows only the events about this file, by its path.
--request-id <id>Shows only the events of one request, by the request_id that an error gave you.
--error-reference <ref>Shows only the events of one error, by the error_reference that the error gave you.
--cursor <cursor>The cursor of the page before, to read the older events. You cannot use it with --follow.
--after <resume>The resume of the page before, to read only the events after it.
--limit <n>The most events on one page, from 1 to 1,000. The default is 100.
--followKeeps printing new events as they come, until you stop it with Ctrl+C.

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

What it prints

The answer is JSON, and events holds the events. When more events are older, cursor names them: give it to --cursor to read the page before. resume marks the newest event: give it to --after to read only what came after it. --follow does this for you, and prints each event on one line.

Where events are kept

In your own terminal, Kater keeps the newest 10,000 events in .kater/operational.sqlite3 in your content root. Kater’s servers keep each event for 7 days. You see only the events that you can read.

See also