Bug 1703414
| Summary: | Pod Overview in cluster console, resouce usage is mismatched | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Aditya Deshpande <adeshpan> | ||||||||
| Component: | Monitoring | Assignee: | Sergiusz Urbaniak <surbania> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Junqi Zhao <juzhao> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 3.11.0 | CC: | agawand, anpicker, aos-bugs, aprajapa, erooth, fbranczy, hgomes, jokerman, mloibl, mmccomas, pkrupa, spadgett, surbania | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | 4.2.0 | ||||||||||
| 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: | 2019-08-26 09:26:38 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
Aditya Deshpande
2019-04-26 11:04:52 UTC
Created attachment 1559029 [details]
cluster-console pod overview
Created attachment 1559030 [details]
grafana K8S compute resources pod dashborad
Created attachment 1559031 [details]
metrics
Do you see this consistently for the router pod and other pods? If you click on the chart, it should take you to the Prometheus UI with the same query. Do you see the same data as console there? Yes. I can see this consistently for router and other pods. Also, the query behind the chart is taking me to the prometheus console and showing the wrong data. This query is addressed actually in https://bugzilla.redhat.com/show_bug.cgi?id=1669410. I already asked on that and opened a separate bug according to the engineer. I will also update this information on the Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1669410 and ask for the wrong CPU usage as well. We have three related BZs in total in this area, I'd suggest we fix all of them at once, by introducing a recording rule for memory/cpu that is used universally across the stack, that way we can have consistency: * https://bugzilla.redhat.com/show_bug.cgi?id=1712912 * https://bugzilla.redhat.com/show_bug.cgi?id=1703414 * https://bugzilla.redhat.com/show_bug.cgi?id=1701856 I'd expect this to be solved in the 4.2 time frame. *** This bug has been marked as a duplicate of bug 1712912 *** |