Update troubleshooting docs (#21538)

* Update troubleshooting

* verbiage change

Co-authored-by: Alex Fornuto <alex.fornuto@goteleport.com>

* remove trailing space

* Update docs/pages/management/admin/troubleshooting.mdx

Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>

---------

Co-authored-by: Alex Fornuto <alex.fornuto@goteleport.com>
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
This commit is contained in:
Steven Martin 2023-02-09 16:19:07 -05:00 committed by GitHub
parent c117091201
commit 98b3de1d55
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -27,8 +27,17 @@ To diagnose problems, you can configure the `teleport` process to run with
verbose logging enabled by passing it the `-d` flag. `teleport` will write logs
to stderr.
Logs will resemble the following (these logs were printed while joining a Node
to a cluster, then terminating the `teleport` process on the Node):
Alternatively, you can set the log level from the Teleport configuration file:
```yaml
teleport:
log:
severity: DEBUG
```
Restart the `teleport` process to apply the modified log level. Logs will resemble
the following (these logs were printed while joining a server to a cluster, then
terminating the `teleport` process on the server):
```
DEBU [NODE:PROX] Agent connected to proxy: [aee1241f-0f6f-460e-8149-23c38709e46d.tele.example.com aee1241f-0f6f-460e-8149-23c38709e46d teleport-proxy-us-west-2-6db8db844c-ftmg9.tele.example.com teleport-proxy-us-west-2-6db8db844c-ftmg9 localhost 127.0.0.1 ::1 tele.example.com 100.92.90.42 remote.kube.proxy.teleport.cluster.local]. leaseID:4 target:tele.example.com:11106 reversetunnel/agent.go:414