From e11996173b5bccc7ad7c9a19af7cfd8231c2f51d Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Thu, 28 Sep 2023 09:48:53 -0700 Subject: [PATCH] Apply PR #880 to version-2.7 docs - [Backport 2.7] Add cattle-cluster-agent trace/debug logs --- .../other-troubleshooting-tips/logging.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/logging.md b/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/logging.md index d4d6353442e..6d0e6dd9b4f 100644 --- a/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/logging.md +++ b/versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/logging.md @@ -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. + +:::