# Traces, metrics and logs in development

**Not built.** This page is the design; Jadpo doesn't do this yet. See [What is built](/docs/debugging-and-review-built.md).

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

| 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](/docs/running-a-service-in-a-container.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 look like those of `jadpo watch` and `jadpo calls`.