Bug 1509525
| Summary: | [RFE] Users would like to see logs and metrics from the Router | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Bruno Andrade <bandrade> |
| Component: | RFE | Assignee: | Eric Paris <eparis> |
| Status: | CLOSED DUPLICATE | QA Contact: | Xiaoli Tian <xtian> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.5.0 | CC: | aos-bugs, jokerman, mmccomas, pweil, rmeggins |
| 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: | 2017-11-22 17:38:59 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: | |||
*** This bug has been marked as a duplicate of bug 1438482 *** |
Description of problem: Would be great if metrics and logs from the HAProxy router could be directed to the OpenShift Log Stack. Of course it ought to respect the RBAC for tenancy. 1. Why exactly do you need this feature? (List the business requirements here) Clients want to: 1. See that router configurations like disabling stickiness through annotations actually take effect 2. See response codes and timing from router for troubleshooting and performance analysis 2. How would you like to achieve this? (List the functional requirements here) I would like the router logs that can be enabled and sent to a syslog server, to be collected and sent to the OpenShift logging service. The logs should be available in the operations index for admins and additionally, the same SNI rules the router uses could be used to split the logs into appropriate indexes for the clients so they can see the logs relevant to their services. 3. Do you have any specific timeline dependencies? The sooner, the better. Clients are asking for the capability and we don't have an alternative method of providing the the data they are asking for. 4. Would you be able to assist in testing this functionality if implemented? yes