Bug 1695655
Summary: | [RFE] Metrics for memory usage of AWS instances needs to be collected from CloudWatch new Agent | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> | ||||||||||||
Component: | C&U Capacity and Utilization | Assignee: | Alexander Zagaynov <azagayno> | ||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Matouš Mojžíš <mmojzis> | ||||||||||||
Severity: | high | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> | ||||||||||||
Priority: | high | ||||||||||||||
Version: | 5.9.4 | CC: | azagayno, bsorota, dmetzger, jprause, mshriver, obarenbo, rchowdry, smallamp | ||||||||||||
Target Milestone: | GA | Keywords: | RFE, ZStream | ||||||||||||
Target Release: | 5.9.9 | ||||||||||||||
Hardware: | Unspecified | ||||||||||||||
OS: | Unspecified | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | 5.9.9.2 | Doc Type: | If docs needed, set a value | ||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | 1684525 | Environment: | |||||||||||||
Last Closed: | 2019-05-29 12:41:11 UTC | Type: | --- | ||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||
Documentation: | --- | CRM: | |||||||||||||
Verified Versions: | Category: | --- | |||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
Cloudforms Team: | AWS | Target Upstream Version: | |||||||||||||
Embargoed: | |||||||||||||||
Bug Depends On: | 1684525 | ||||||||||||||
Bug Blocks: | |||||||||||||||
Attachments: |
|
Comment 2
CFME Bot
2019-04-03 15:01:25 UTC
Hi, I have tried installing the hotfix provided for CFME Version:5.9.9.1 to fix the memory reporting issue but even after applying the same we are not able to see the memory metrics in dashboard cfme-gemset-5.9.9.1-2.el7cf.x86_64.rpm. Apart from this the customer is running version 5.9.4.7 and there is no option to upgrade since lot of customization has been done and looking for hotfix for specific cfme version 5.9.4.7. Hi Ravikanth, did you setup CloudWatch agent on the target instances? Created attachment 1567821 [details]
memory screenshot from AWS console
Created attachment 1567822 [details]
CFME screenshot
Hi Alexander, Yes i did install CWagent in AWS and able to see metrics in AWS console. Attaching screenshots for reference. 1) Please set equal time frames on both screens to avoid confusing. 2) You looking at "MemoryUsed" counter, but we gather "MemoryUtilization" https://github.com/ManageIQ/manageiq-providers-amazon/blob/9d1567e0816e583493924a13b4419b109d23d3a9/app/models/manageiq/providers/amazon/cloud_manager/metrics_capture.rb#L24 1) Please set equal time frames on both screens to avoid confusing. Still the counter shows 0 across timeframe since its enabled 2) You looking at "MemoryUsed" counter, but we gather "MemoryUtilization" https://github.com/ManageIQ/manageiq-providers-amazon/blob/9d1567e0816e583493924a13b4419b109d23d3a9/app/models/manageiq/providers/amazon/cloud_manager/metrics_capture.rb#L24 Both Memoryused and Utilizations counters are Zero bytes in CFME dashboard I can't see that, please show me screenshots, or better find me in gchat to solve your issue faster. Created attachment 1568739 [details]
Memory used cwagent for 05-14-19
Created attachment 1568740 [details]
Memory avlb cwagent for 05-14-19
Created attachment 1568741 [details]
Memory avlb 0 bytes for 05-14-19
Hi Alexander, I have attached screenshots captured for full day on 05/14/19 for both CWagent in AWS console and CFME dashboard(it show 0 bytes) Verified in 5.9.9.2 It collects memory metrics correctly. EBS disk metrics are not collected. Hi, I am not able to update the cfme to 5.9.9.2 since its not publicly available and i am only able to upgrade to 5.9.9.1 and confirm that metrics collection doesn't work even after applying the hotfix. Can we have hotfix for cfme version 5.9.4 since that's the version the customer is running the cfme on and they will not be able to upgrade the cfme to 5.9.9.2 considering the amount of customizations done and need the metrics fixed for this 5.9.4 version only. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1289 |