Inspect logs

SQD Cloud automatically collects the logs emitted by the squid processor, its API server and its database. Please use the built-in SDK logger throughout your code when developing for SQD Cloud. You can set the severity flags for squids running in the Cloud via SQD_DEBUG, SQD_TRACE or SQD_INFO - see Environment Variables. To inspect and follow the squid logs from all the squid services, use sqd logs:

sqd logs -n <name> -s <slot> -f

sqd logs -n <name> -t <tag> -f

There are additional flags to filter the logs:

-f to follow the logs
-c filters by container: processor, api, query-node, db-migrate, or db
-l allows filtering by the severity
-p number of lines to fetch (default: 100)
--since sets the time range (default: 1d), such as 1d, 10h, or 30m
--search filters by message content

Example

sqd logs -r my-org/my-squid:production \
  -c processor -l info --since 1d --search "processed"

For an incident, start with a bounded time range and the first error:

sqd logs -n <name> -s <slot> -c processor -l error --since 2h

Include the organization, squid name, exact slot, processor name, time range, and a short surrounding log window in support requests. Do not include secrets or database URLs.

Managed

Self-Hosting

Example

​Example

Example