OpenShift Logging Levels: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
 
(One intermediate revision by the same user not shown)
Line 13: Line 13:
At installation, the log level for OpenShift processes ([[OpenShift_Runtime#master_Daemons|master daemons]],  [[OpenShift_Runtime#node_Daemon|node daemons]]) can be configured at installation by setting [[OpenShift_hosts#debug_level|debug_level]] in the Ansible inventory file.
At installation, the log level for OpenShift processes ([[OpenShift_Runtime#master_Daemons|master daemons]],  [[OpenShift_Runtime#node_Daemon|node daemons]]) can be configured at installation by setting [[OpenShift_hosts#debug_level|debug_level]] in the Ansible inventory file.


At runtime, OpenShift components log levels is specified in systemd configuration files, and can be controlled via their --loglevel parameter. This parameter can be set in the OPTIONS for the relevant component's configuration within /etc/sysconfig. After changing the log level, restart with  
At runtime, OpenShift components log levels is specified in systemd configuration files, and can be controlled via their --loglevel parameter. This parameter can be set in the OPTIONS for the relevant component's configuration within /etc/sysconfig:
 
OPTIONS=--loglevel=4
 
After changing the log level, restart with  


  systemctl restart <''component-name''>
  systemctl restart <''component-name''>

Latest revision as of 19:12, 21 November 2017

External

Internal

Overview

Change the Log Level for OpenShift Processes

At installation, the log level for OpenShift processes (master daemons, node daemons) can be configured at installation by setting debug_level in the Ansible inventory file.

At runtime, OpenShift components log levels is specified in systemd configuration files, and can be controlled via their --loglevel parameter. This parameter can be set in the OPTIONS for the relevant component's configuration within /etc/sysconfig:

OPTIONS=--loglevel=4

After changing the log level, restart with

systemctl restart <component-name>

For more details see:

Log levels:

  • 0: Disabled
  • 1: Errors
  • 2: Warnings
  • 3: Info
  • 4: Verbose
  • 5: Debug