# Traces, metrics and logs in development

In development, your app's telemetry, its traces, metrics and logs, stays
on your machine ([Telemetry](telemetry.md)).
`jadpo dev --export-telemetry` sends it on to a collector. You read it from
the command line, as you read the call log:

| Command | Shows |
|---|---|
| `jadpo traces` | Recent requests, schedule runs and deliveries, one line each, opening into `jadpo trace <id>` |
| `jadpo metrics` | The metrics the runtime records and your app's own (`monitoring.jadpo`), per route, action or path |
| `jadpo logs` | Your app's logs, including those of its [services](what-package-code-may-do.md#services), by level |

Each command takes the same filters: by route, action, domain, path,
failure and slowness (`--slower-than 200ms`). `--follow` keeps printing
as new entries arrive, and `--json` gives the output as data. The
developer console will show the same data.

These commands' screens follow the
[CLI design language](https://github.com/jadpo-dev/jadpo/blob/main/docs/cli-design-language.md), as the screens of
`jadpo watch` and `jadpo calls` do.