Bug 1367913 - Memory, disk, network metrics not being collected from Azure instances
Summary: Memory, disk, network metrics not being collected from Azure instances
Keywords:
Status: CLOSED DUPLICATE of bug 1375324
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: C&U Capacity and Utilization
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.7.0
Assignee: Bronagh Sorota
QA Contact: Nandini Chandra
URL:
Whiteboard: azure:c&u
Depends On:
Blocks: 1370616
TreeView+ depends on / blocked
 
Reported: 2016-08-17 19:08 UTC by Nandini Chandra
Modified: 2016-10-28 15:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1370616 (view as bug list)
Environment:
Last Closed: 2016-09-23 13:25:30 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Nandini Chandra 2016-08-17 19:08:19 UTC
Description of problem:
-----------------------
It looks like CFME is only collecting CPU usage for Azure instances.Memory,disk and network metrics are not being collected for Azure instances.

#psql -d vmdb_production
1)vmdb_production=# select * from metrics where resource_name = 'TestRmVMOne' and derived_memory_used != 0\x\g\x
Expanded display is on.
(No rows)
2)vmdb_production=# select * from metrics where resource_name = 'TestRmVMOne' and disk_usage_rate_average != 0\x\g\x
Expanded display is on.
(No rows)
3)
vmdb_production=# select cpu_usage_rate_average  from metrics where resource_name = 'TestRmVMOne' and cpu_usage_rate_average != 0\x\g\x
Expanded display is on.
-[ RECORD 1 ]----------+---------
cpu_usage_rate_average | 0.250271
-[ RECORD 2 ]----------+---------
cpu_usage_rate_average | 0.250271


Version-Release number of selected component (if applicable):
------------------------
5.6.1.2


How reproducible:
-----------------
Always


Steps to Reproduce:
-------------------
1.Manage Azure.Enable C&U collection for Azure.
2.Check the DB for metrics collection.


Actual results:
---------------
Memory, disk, network metrics not being collected from Azure instances.


Expected results:
-----------------
Memory, disk, network metrics should be collected from Azure instances.


Additional info:
----------------
Not sure if Azure makes a distinction between Linux and Windows instances.
I've tested Windows instances.On the Azure Portal, I can see graphs for
these metrics for Windows instances:  CPU, memory, disk read, disk write disk read and write.No graphs for network usage were displayed on the Azure Portal.

Comment 2 Bronagh Sorota 2016-08-18 12:10:14 UTC
Hi Nandini,
Support for disk, memory and network utilization was just merged upstream on Tuesday so I'm not sure the build you are using has it. Can you give me your appliance IP and I will take a look?

Thank you
Bronagh

Comment 3 Nandini Chandra 2016-08-18 21:10:00 UTC
Bronagh,

This was 5.6.1.2.Going by what you said, that wouldn't have support for disk, memory and network utilization.

Comment 4 Bronagh Sorota 2016-08-24 16:13:11 UTC
Can this be closed?

Comment 5 Dave Johnson 2016-08-26 19:19:35 UTC
Closed incorrectly... reopening...

This one moves to post for verification on 5.7.  We also need to clone this to 5.6.z and get the fix backported.

Comment 6 Bronagh Sorota 2016-08-30 14:51:37 UTC
Nandini
As i mentioned above, enhanced metric support was merged upstream the day before you opened this BZ so you might not have a build with this functionality in place. Can you confirm? Or give me the IP of your appliance so I can confirm.

Bronagh

Comment 7 Nandini Chandra 2016-08-30 18:14:41 UTC
Bronagh,

This BZ has been kept open so that it can be verified when 5.7 is made available for testing.

Comment 8 Bronagh Sorota 2016-09-23 13:25:30 UTC
hi Nandini
this appears to be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1375324
Therefore I am closing this one.

Bronagh

*** This bug has been marked as a duplicate of bug 1375324 ***


Note You need to log in before you can comment on or make changes to this bug.