Bug 1304888

Summary: [RFE] Implementing Aggregating Container status check.
Product: OpenShift Container Platform Reporter: Ryan Howe <rhowe>
Component: RFEAssignee: Luke Meyer <lmeyer>
Status: CLOSED CURRENTRELEASE QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1.0CC: aos-bugs, jcantril, jokerman, lmeyer, mmccomas, pdwyer
Target Milestone: ---   
Target Release: 3.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-19 17:26:46 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 Ryan Howe 2016-02-04 22:09:45 UTC
Description of problem:

We need a feature that would allow us to check to ensure that the logging stack was configured and working as designed. We are not looking to check the health of the pods. 

This request is asking for a status check on the EFK stack to ensure that the console is workings, the logs are being gathered, and the storage is healthy.

Comment 1 Luke Meyer 2016-02-08 21:19:56 UTC
That would be a great addition to diagnostics.

It would probably be pretty complicated.

Comment 2 Jeff Cantrill 2016-02-09 14:14:57 UTC
I think we talked about it, but couldnt some variance of https://github.com/openshift/origin-aggregated-logging/blob/master/hack/testing/check-EFK-running.sh provide similiar results?  Maybe it could be modified to be useful in the interim until a proper diagnostic solution could be created.

Comment 3 Dan McPherson 2016-04-13 19:04:33 UTC
Should this not be done through liveness/readiness?