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

Bug 1339554

Summary: Warning 'Discover:"logging.*" is not configured pattern' on kibana console
Product: OpenShift Container Platform Reporter: chunchen <chunchen>
Component: Management ConsoleAssignee: Jessica Forrester <jforrest>
Status: CLOSED CURRENTRELEASE QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: medium    
Version: 3.2.0CC: aos-bugs, chunchen, ewolinet, javier.ramirez, jokerman, mmccomas, tdawson, wsun, xiazhao
Target Milestone: ---Keywords: Regression
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: 2016-09-07 21:28:58 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:
Attachments:
Description Flags
warning kibana console none

Description chunchen 2016-05-25 10:02:53 UTC 
Description of problem:
It show below warnings on kibana console
'Discover:"logging.*" is not configured pattern.Using the default index pattern "logging.<project-uuid>.*"'

Version-Release number of selected component (if applicable):
brew-pulp-docker01..../openshift3/logging-auth-proxy      3.2.0
brew-pulp-docker01..../openshift3/logging-elasticsearch   3.2.0
brew-pulp-docker01..../openshift3/logging-fluentd         3.2.0
brew-pulp-docker01..../openshift3/logging-kibana          3.2.0


How reproducible:
always

Steps to Reproduce:
1. Login to OpenShift and create a project
oc new-project logging

2. Deploy EFK stack

3. Log into OpenShift web console and navigate to a pod, then click "Logs" tab -> click "View archive"

4. Check the kibana console

Actual results:
Show warning message, please refer to the screenshot in attachment

Expected results:
Should not show such warning message

Additional info:
Comment 1 chunchen 2016-05-25 10:05:00 UTC 
we can now search kibana with both
"kubernetes_pod_name: logging-fluentd-1-r9ejs && kubernetes_namespace_name: logging"
and
"kubernetes_pod_name: logging-fluentd-1-r9ejs && kubernetes_namespace_name: logging.545246c5-224a-11e6-8380-fa163efb215f.* "

so, end user should not be warned like this.
Comment 2 chunchen 2016-05-25 10:07:55 UTC 
Created attachment 1161374 [details]
warning kibana console
Comment 3 Luke Meyer 2016-05-25 19:42:04 UTC 
Eric any idea what is causing this?
Comment 4 ewolinet 2016-05-25 19:50:15 UTC 
This may be related to how the console is sending the user to the Kibana page.  What is the full URL when clicking on "View Archive"?  I'm curious as to whether or not it contains a reference to using "logging.*" as the index.

The "kubernetes_namespace_name" should only be "logging".  When we create the index in Elasticsearch we now append the namespace UUID which is what we see for the default index pattern.
Comment 8 Jeff Cantrill 2016-08-29 19:27:01 UTC 
*** Bug 1371108 has been marked as a duplicate of this bug. ***