Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1640878

Summary: [DOCS] How to set log level for controller and api both
Product: OpenShift Container Platform Reporter: Miheer Salunke <misalunk>
Component: DocumentationAssignee: Michael Burke <mburke>
Status: CLOSED CURRENTRELEASE QA Contact: Anping Li <anli>
Severity: urgent Docs Contact: Vikram Goyal <vigoyal>
Priority: urgent    
Version: 3.11.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-26 16:09:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Miheer Salunke 2018-10-19 04:11:42 UTC
Document URL: 

https://docs.openshift.com/container-platform/3.11/install_config/master_node_configuration.html#master-node-config-logging-levels

Section Number and Name: 

Describe the issue: 

https://docs.openshift.com/container-platform/3.11/install_config/master_node_configuration.html#master-node-config-logging-levels


Suggestions for improvement: 

"Edit the /etc/sysconfig/atomic-openshift-master" -> 

but /etc/sysconfig/atomic-openshift-master   does not exist from 3.10

In the masters ->

vi /etc/origin/master/master.env

DEBUG_LOGLEVEL=6

master-restart api controller

Also we shall check if it sets the logs level for the controller and api both.



"You can control which INFO messages are logged by setting the loglevel option in the in node configuration files, the /etc/origin/master/master-config.yaml file."

I don't have any idea how to set it. 

Additional information: