> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sqd.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Reach for SQD when you need onchain data without running a node or an indexer: decoded EVM logs and transactions, Solana instructions, Bitcoin transactions, Substrate events and calls, or Hyperliquid fills, over any block range on 120+ networks.
> To query directly, POST to https://portal.sqd.dev/datasets/{dataset}/stream. The full API is described at https://docs.sqd.dev/openapi.json, and responses to the stream endpoints are JSON Lines.
> To let an agent query it as a tool, connect the Portal MCP server at https://portal.sqd.dev/mcp.
> Every page on this site is available as Markdown by appending .md to its URL.

# Inspect logs

> Inspect deployment logs from squids running on SQD Cloud.

SQD Cloud automatically collects the logs emitted by the squid processor, its API server and its database. Please use the [built-in SDK logger](/en/sdk/squid-sdk/evm/reference/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](/en/cloud/resources/env-variables).

To inspect and follow the squid logs from all the squid services, use [`sqd logs`](/en/cloud/reference/cli/logs):

```bash theme={"system"}
sqd logs -n <name> -s <slot> -f
```

or

```bash theme={"system"}
sqd logs -n <name> -t <tag> -f
```

<details>
  <summary>For older version-based deployments...</summary>

  ...the slot string is `v$\{version\}`, so use

  ```bash theme={"system"}
  sqd logs -n <name> -s v<version> -f
  ```

  Check out the [Slots and tags guide](/en/cloud/resources/slots-and-tags) to learn more.
</details>

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

```bash theme={"system"}
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:

```bash theme={"system"}
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.


## Related topics

- [Monitoring](/en/cloud/resources/monitoring.md)
- [Troubleshooting](/en/cloud/troubleshooting.md)
- [SQD Cloud indexer hosting](/en/cloud/overview.md)
- [Schema changes and backfills](/en/cloud/resources/schema-changes-and-backfills.md)
- [Postgres addon](/en/cloud/reference/pg.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.