apunkt/ktx
1
0
Fork 0
mirror of https://github.com/Kaelio/ktx.git synced 2026-06-07 07:55:13 +02:00
Code Issues Projects Releases Packages Wiki Activity

docs: align ingest trace guidance with public CLI

Browse source
This commit is contained in:
Andrey Avtomonov 2026-05-18 09:45:14 +02:00
parent fdd66ebf59
commit cfcb91d444
1 changed files with 9 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs-site/content/docs/cli-reference/ktx-ingest.mdx
View file

@ -113,11 +113,15 @@ results.
## Inspect source ingest traces
Source ingest writes persistent JSONL traces for postmortem debugging. Stored
ingest status prints the trace path near the run identifiers:
Source ingest writes persistent JSONL traces for postmortem debugging. Plain
ingest output prints the trace path near the report, run, and job identifiers
when a trace is available:
```bash
ktx ingest status <runId>
```text
Report: report-abc123
Run: run-abc123
Job: job-abc123
Trace: .ktx/ingest-traces/job-abc123/trace.jsonl
```
The trace file lives under the project directory at
@ -125,8 +129,7 @@ The trace file lives under the project directory at
job id, run id, sync id, connection id, source key, phase, event name, timing,
state snapshot, decision context, and error details. Failed runs also write a
stored ingest report with `status: "failed"`, `failure.phase`,
`failure.message`, and the same trace path, so `ktx ingest status <runId>` can
point you to the postmortem trace.
`failure.message`, and the same trace path.
Use `jq` or line-oriented tools to inspect a trace: