Ask Your Question
0

devstack->how to collect host CPU metric using ceilometer [closed]

asked 2016-01-09 17:09:43 -0500

Sandeep gravatar image

updated 2016-01-10 07:53:28 -0500

Syed Awais Ali gravatar image

installed devstack+ceilometer and enabled all required property but not able to see CPU related metric like compute.node.cpu.frequency ,compute.node.cpu.percent

nova.conf->

compute_monitors = ComputeDriverCPUMonitor
notification_driver = nova.openstack.common.notifier.rpc_notifier
notification_driver = ceilometer.compute.nova_notifier
notification_driver = nova.openstack.common.notifier.rabbit_notifier
notification_driver=messagingv2
compute_manager = nova.compute.manager.ComputeManager

ceilometer sample-list -m compute.node.cpu

+-------------+------+------+--------+------+-----------+
| Resource ID | Name | Type | Volume | Unit | Timestamp |
+-------------+------+------+--------+------+-----------+
+-------------+------+------+--------+------+-----------+

ceilometer meter-list

+---------------------------------+------------+-----------+----------------------------------------------+----------------------------------+----------------------------------+
| Name                            | Type       | Unit      | Resource ID                                  | User ID                          | Project ID                       |
+---------------------------------+------------+-----------+----------------------------------------------+----------------------------------+----------------------------------+
| cpu                             | cumulative | ns        | 638becc8-21c3-49ed-b9fc-9d0ca453dba7         | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| cpu                             | cumulative | ns        | d926a97a-2499-49df-8362-32dbc7900fb7         | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| disk.allocation                 | gauge      | B         | 638becc8-21c3-49ed-b9fc-9d0ca453dba7         | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| disk.allocation                 | gauge      | B         | d926a97a-2499-49df-8362-32dbc7900fb7         | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| disk.capacity                   | gauge      | B         | 638becc8-21c3-49ed-b9fc-9d0ca453dba7         | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| disk.capacity                   | gauge      | B         | d926a97a-2499-49df-8362-32dbc7900fb7         | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| disk.device.allocation          | gauge      | B         | 638becc8-21c3-49ed-b9fc-9d0ca453dba7-hdd     | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| disk.device.allocation          | gauge      | B         | 638becc8-21c3-49ed-b9fc-9d0ca453dba7-vda     | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| disk.device.allocation          | gauge      | B         | d926a97a-2499-49df-8362-32dbc7900fb7-hdd     | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| disk.device.allocation          | gauge      | B         | d926a97a-2499-49df-8362-32dbc7900fb7-vda     | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| disk.device.allocation          | gauge      | B         | d926a97a-2499-49df-8362-32dbc7900fb7-vdb     | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| disk.device.capacity            | gauge      | B         | 638becc8-21c3-49ed-b9fc-9d0ca453dba7-hdd     | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| disk.device.capacity            | gauge      | B         | 638becc8-21c3-49ed-b9fc-9d0ca453dba7-vda     | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| disk.device.capacity            | gauge      | B         | d926a97a-2499-49df-8362-32dbc7900fb7-hdd     | 6e1cf83ed56e4326bd27e5e008a88ada | 44efa37925344d1089330a9bb3e7c27e |
| disk.device.capacity            | gauge      | B
edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Sandeep
close date 2016-01-11 13:25:21.904070

add a comment

2 answers

Sort by ยป oldest newest most voted
0

answered 2016-01-10 20:49:01 -0500

Mohit gravatar image

This might help - https://ask.openstack.org/en/question...

edit flag offensive delete link more
add a comment
0

answered 2016-01-11 13:24:27 -0500

Sandeep gravatar image

thanks i found solution by using compute monitor as nova.virt http://docs.openstack.org/liberty/con... compute_monitors = (ListOpt) A list of monitors that can be used for getting compute metrics. You can use the alias/name from the setuptools entry points for nova.compute.monitors.* namespaces. If no namespace is supplied, the "cpu." namespace is assumed for backwards-compatibility. An example value that would enable both the CPU and NUMA memory bandwidth monitors that used the virt driver variant: ["cpu.virt_driver", "numa_mem_bw.virt_driver"] compute_monitors =nova.compute.monitors.cpu.virt_driver

edit flag offensive delete link more
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2016-01-09 17:09:43 -0500

Seen: 811 times

Last updated: Jan 11 '16