Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v9] Allow custom trace exporter for tsh #19588

Merged
merged 3 commits into from Dec 27, 2022
Merged

Conversation

rosstimothy
Copy link
Contributor

Backport #19405 to branch/v9

@rosstimothy rosstimothy changed the title Allow custom trace exporter for tsh [v9] Allow custom trace exporter for tsh Dec 21, 2022
@rosstimothy rosstimothy marked this pull request as ready for review December 21, 2022 21:35
@github-actions github-actions bot added size/md tsh tsh - Teleport's command line tool for logging into nodes running Teleport. labels Dec 21, 2022
Copy link
Contributor

@jakule jakule left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we first fix the flaky test before backporting the changes to release branches?

Copy link
Contributor

@jakule jakule left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like the test failure is related to #19597 and not this test itself.

@github-actions github-actions bot removed the request for review from zmb3 December 22, 2022 17:01
@rosstimothy rosstimothy enabled auto-merge (squash) December 27, 2022 14:37
rosstimothy and others added 2 commits December 27, 2022 12:10
Trace forwarding via `tsh --trace` only works to date if Auth is
configured with the `tracing_service` enabled. In all other scenarios
the traces are still forwarded to Auth but are silently dropped.
This makes it difficult to capture valuable traces from customers
with latency issues as they are first required to setup a Telemetry
backend and enable tracing in their cluster.

A new `--trace-exporter` flag is added to `tsh` to make it possible
to direct traces from `tsh` to a file or local instance of jaeger
without hacing to modify their Teleport cluster. The url must follow
the same semantics as the config file equivalent.

One important caveat is that **only** the `tsh` spans will be captured.
Any corresponding `teleport` spans are exported acording to the
`tracing_service`. While this only paints half the picture, it is
still a good indicator of where `tsh` may be experiencing latency.

An example usage to send traces to local files:

```bash
tsh --trace --trace-exporter=file:///some/path/traces ssh user@foo
```
@rosstimothy rosstimothy merged commit 81be2d3 into branch/v9 Dec 27, 2022
@rosstimothy rosstimothy deleted the tross/backport-19405/v9 branch December 27, 2022 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport size/md tsh tsh - Teleport's command line tool for logging into nodes running Teleport.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants