Bug 1887907

Summary:	No results in Kibana when pressing "Show in Kibana..." for logging infrastructure pods
Product:	OpenShift Container Platform	Reporter:	Eran Raichstein <eraichst>
Component:	Documentation	Assignee:	Petr Kovar <pkovar>
Status:	CLOSED NEXTRELEASE	QA Contact:	Xiaoli Tian <xtian>
Severity:	low	Docs Contact:	Petr Kovar <pkovar>
Priority:	unspecified
Version:	4.5	CC:	aos-bugs, jcantril
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:	2022-06-10 18:20:39 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 Eran Raichstein 2020-10-13 14:59:09 UTC

Description of problem:
When pressing the "Show in Kibana..." button for pods that are part of the logging infrastructure (==elastic, fluentd etc.) you get empty results in Kibana.

(logs from those pods are filtered out from logging ... so having that button is misleading )

Version-Release number of selected component (if applicable):
4.5+

How reproducible:
Press the "Show in Kibana..." button for pods that are part of the logging infrastructure (after installing cluster-logging-operator)

Actual results:
empty results in Kibana

Expected results:
BEST #1: That the button would not exist for none-relevant pods 
BEST #2: start logging info also for the logging infrastructure (as long as this do not creates logs loop)
LOW: Some information in documentation that explain the behavior 

Additional info:

Link to slack thread 
https://coreos.slack.com/archives/GGUR75P60/p1602600210235900?thread_ts=1602598206.225200&cid=GGUR75P60

Comment 1 Jeff Cantrill 2020-10-13 15:16:12 UTC

(In reply to Eran Raichstein from comment #0)
> Description of problem:
> When pressing the "Show in Kibana..." button for pods that are part of the
> logging infrastructure (==elastic, fluentd etc.) you get empty results in
> Kibana.
> 
> (logs from those pods are filtered out from logging ... so having that
> button is misleading )

There is no mechanism AFAIK to filter this message in the console

Moving to document and why (to avoid a feedback loop when ingesting logs)