[Backport 2.7] Add cattle-cluster-agent trace/debug logs (#880)

* add cattle-cluster-agent trace/debug logs

* Update docs/troubleshooting/other-troubleshooting-tips/logging.md

Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>

* Update docs/troubleshooting/other-troubleshooting-tips/logging.md

Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>

* Update docs/troubleshooting/other-troubleshooting-tips/logging.md

Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>

* Update docs/troubleshooting/other-troubleshooting-tips/logging.md

Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>

---------

Co-authored-by: Marty Hernandez Avedon <marty.avedon@suse.com>
This commit is contained in:
Felipe Colussi-oliva
2023-09-28 12:45:50 -04:00
committed by GitHub
co-authored by Marty Hernandez Avedon
parent 79cd5aeaae
commit fcda4e87d9
@@ -78,3 +78,19 @@ possible to enable debug logs in `rancher-machine` when provisioning RKE1, RKE2
Just like the `trace` log level above, `rancher-machine` debug logs can contain sensitive information.
:::
## Cattle-cluster-agent debug logs
The `cattle-cluster-agent` log levels can be set when you initialize downstream clusters.
When you create a cluster under **Cluster Configuration > Agent Environment Vars** you can set variables to define the log level.
- Trace-level logging: Set `CATTLE_TRACE` or `RANCHER_TRACE` to `true`
- Debug-level logging: Set `CATTLE_DEBUG` or `RANCHER_DEUBG` to `true`
:::caution
The `cattle-cluster-agent` debug logs may contain sensitive information.
:::