# komrad log

Show the log lines the server wrote under one trace id

[komrad](https://komrad.dev/latest/cli.md)

```bash
komrad log [trace-id] [flags]
```

Every line the server logs carries a trace id, which is one id for one request end to end or one pass of a background loop. A call that fails answers with its trace id, so following what happened behind a failure is a matter of naming the id here. The server reads its own log back, so this works against a remote engine the same as against this machine.

Run with --recent instead of an id to list the trace ids the log ends with, which is where to start when you know what you did but not what it was called.

## Flags

| Flag | Type | Description |
| --- | --- | --- |
| [`--recent`](https://komrad.dev/latest/cli/log.md#flag-recent) | bool | list the trace ids the log ends with rather than showing one |

## Inherited flags

| Flag | Type | Description |
| --- | --- | --- |
| [`--config`](https://komrad.dev/latest/cli/log.md#inherited-config) | stringArray | path to a config TOML, repeatable, later files win over earlier ones |
| [`--engine`](https://komrad.dev/latest/cli/log.md#inherited-engine) | string | engine to reach: local for this machine, or a file in the config's engines directory, layered over the config |
