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

[v14] docs: remove old versions ref #32865

Merged
merged 2 commits into from
Oct 2, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/pages/architecture/tls-routing.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,7 @@ TLS extensions.

## How it works

Starting from version `8.0` Teleport proxy listens for all client connections
on its `web_listen_addr` by default:
The Teleport Proxy Service listens for all client connections on its `web_listen_addr` by default:

```yaml
proxy_service:
Expand Down
5 changes: 1 addition & 4 deletions docs/pages/management/diagnostics/tracing.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,6 @@ tracing_service:
sampling_rate_per_million: 1000000
```

Please note that tracing was added in the following versions: 8.3.18, 9.3.15, and 10.1.0. Enabling the above configuration
on a version prior to the versions with tracing support will result in a failure to parse the config file.

### Sampling rate

It is important to choose the sampling rate wisely. Sampling at a rate of 100% could have a negative impact on the
Expand Down Expand Up @@ -71,4 +68,4 @@ format as the `exporter_url` of the `tracing_service`.
```code
$ tsh --trace --trace-exporter=grpc://collector.example.com:4317 ssh root@myserver
$ tsh --trace --trace-exporter=file:///var/lib/teleport/traces ls
```
```
Loading