Bug 1305574

Summary: [docs] kibana - no step to restart Master after setting loggingPublicURL
Product: OpenShift Container Platform Reporter: Evgheni Dereveanchin <ederevea>
Component: DocumentationAssignee: Vikram Goyal <vigoyal>
Status: CLOSED NOTABUG QA Contact: Vikram Goyal <vigoyal>
Severity: unspecified Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 3.1.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://access.redhat.com/documentation/en/openshift-enterprise/3.1/installation-and-configuration/chapter-17-aggregating-container-logs#kibana
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-30 14:41:11 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:

Description Evgheni Dereveanchin 2016-02-08 15:42:22 UTC 
Document URL: 
https://access.redhat.com/documentation/en/openshift-enterprise/3.1/installation-and-configuration/chapter-17-aggregating-container-logs#kibana

Section Number and Name: 
 17.4.3. Kibana
Describe the issue: 
 this section describes how to edit master-config.yaml however there's no mention that changes will take effect only after the master is restarted

Suggestions for improvement: 
Add a note to restart the master after editing master-config.yaml