Bug 1466494
Summary: | [dedicated][RFE] Aggregate router logs | ||
---|---|---|---|
Product: | OpenShift Online | Reporter: | Steven Walter <stwalter> |
Component: | RFE | Assignee: | Abhishek Gupta <abhgupta> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.x | CC: | abhgupta, nraghava, sspeiche, stwalter, tkatarki, whearn |
Target Milestone: | --- | Keywords: | OnlineDedicated |
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-09-25 14:16:00 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
Steven Walter
2017-06-29 19:48:02 UTC
Good morning! This RFE has been opened for over 4 weeks and has not yet been triaged. (I.e. the pm_ack, devel_ack and qa_ack flags get set.) Is that something that should have happened, by now, for this ticket? Thanks. Primary cause is being working (alerting ops when kibana web console isn't responding whether it is router issue or other), so this will minimize the need for this feature. Feel free to close if no longer needed. I will check into creating a card on the Trello board to track this but see it as pretty low level priority as ops will be monitoring this themselves. If we find other use cases or customers who want this, it would bump it up a bit. I need someone from ops to highlight how router logs are captured today. Adding bign for that. + Wesley to provide the relevant information As for today they are captured just like every other pod log(through fluentd). They are stored so only cluster admins can see them, which means we have to manually use curl to access the logs, not something OPs has documented. Though even with that I don't think router logs are overly helpful as it is mostly just logging when the router refreshes its cache of routes. I believe this can be accomplished by getting access view the tier access for SREs and CEE folks. The will give them cluster reader rights to they have access to logs for all pods. See https://mojo.redhat.com/docs/DOC-1144200 I believe tiered access satisfies this RFE and this can be closed. That would work, agreed, I think. |