Skip to content

Commit 2dbbbd0

Browse files
committed
[doc] add missing command to xs-trace
Signed-off-by: Guillaume <[email protected]>
1 parent b029809 commit 2dbbbd0

File tree

1 file changed

+5
-2
lines changed
  • doc/content/toolstack/features/Tracing

1 file changed

+5
-2
lines changed

doc/content/toolstack/features/Tracing/index.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -81,14 +81,17 @@ and also assist newcomers in onboarding to the project.
8181

8282
By default, traces are generated locally in the `/var/log/dt` directory. You can copy or forward
8383
these traces to another location or endpoint using the `xs-trace` tool. For example, if you have
84-
a *Jaeger* server running locally, you can run:
84+
a *Jaeger* server running locally, you can copy a trace to an endpoint by running:
8585

8686
```sh
87-
xs-trace /var/log/dt/ http://127.0.0.1:9411/api/v2/spans
87+
xs-trace cp /var/log/dt/ http://127.0.0.1:9411/api/v2/spans
8888
```
8989

9090
You will then be able to visualize the traces in Jaeger.
9191

92+
The `xs-trace` tool also supports trace files in `.ndjson` and compressed `.zst` formats, so
93+
you can copy or forward these files directly as well.
94+
9295
### Tagging Trace Sessions for Easier Search
9396

9497
#### Specific attributes

0 commit comments

Comments
 (0)