Files
rancher-docs/archived_docs/en/version-2.5/troubleshooting/other-troubleshooting-tips/logging.md
T
Lucas Saintarbor 8c76072fd2 Archive v2.5 docs (#1634)
* Update docusaurus.config.js/Remove v2.5 redirects and update v2.5 label and path

* Update version-2.5-sidebars.json with notice

* Remove v2.5 files/Add v2.5 files to archived_docs folder

* Fix broken link

* Fix broken link/typo

* Fix broken links
2025-02-18 14:08:09 -08:00

1.5 KiB

title
title
Logging
<head> </head>

The following log levels are used in Rancher:

Name Description
info Logs informational messages. This is the default log level.
debug Logs more detailed messages that can be used to debug.
trace Logs very detailed messages on internal functions. This is very verbose and can contain sensitive information.

How to configure a log level

Kubernetes install

  • Configure debug log level
$ KUBECONFIG=./kube_config_cluster.yml
$ kubectl -n cattle-system get pods -l app=rancher --no-headers -o custom-columns=name:.metadata.name | while read rancherpod; do kubectl -n cattle-system exec $rancherpod -c rancher -- loglevel --set debug; done
OK
OK
OK
$ kubectl -n cattle-system logs -l app=rancher -c rancher
  • Configure info log level
$ KUBECONFIG=./kube_config_cluster.yml
$ kubectl -n cattle-system get pods -l app=rancher --no-headers -o custom-columns=name:.metadata.name | while read rancherpod; do kubectl -n cattle-system exec $rancherpod -c rancher -- loglevel --set info; done
OK
OK
OK

Docker Install

  • Configure debug log level
$ docker exec -ti <container_id> loglevel --set debug
OK
$ docker logs -f <container_id>
  • Configure info log level
$ docker exec -ti <container_id> loglevel --set info
OK