Open Stack

Hi
Well, i am also trying to decode all the meters that ceilometer can return, and how to do most of the queries, but, to query some specific data, what I am doing is:Firs get the resource id number and then query using parameters in the curl command.
This is what I already tested:Get the resource id from what you want to query ceilometer
$ curl -X GET -H 'X-Auth-Token:<my_token_here' "http://localhost:8777/v2/resources | python -mjson.tool"   
And then query with: 
$curl -X GET -H 'X-Auth-Token:<my_token_here' "http://localhost:8777/v2/meters/cpu?q.field=resource_id&q.value=<resource_id_here> | python -mjson.tool"
Remember that option "q" is to filter rules for the resources to be returned, and try to use python mjson.tool, just for having something legible in your terminal.
Good luck :)
Cláudio Marques
claudio at onesource.pthttp://www.onesource.pt/

Date: Thu, 20 Jun 2013 16:03:00 +0530
From: jobin.rv at gmail.com
To: claudio at onesource.pt
CC: openstack at lists.launchpad.net
Subject: Re: [Openstack] How to query ceilometer to get nova-specific data

Hey, Claudio!

The command I executed is the second command in the page that you gave(which
 is also the one I am referring to). Can you please pin-point what is 
the mistake in the command or counsel what is the right one to get 
nova-specific data? By the way, I replaced resource_id with the actual ID of the resource I wanted.



On Thu, Jun 20, 2013 at 3:50 PM, claudio marques <claudio at onesource.pt> wrote:




Hi Jobin
I think that your Curl command is not right. Look into this page for more info about meters from ceilometer. 
http://docs.openstack.org/developer/ceilometer/webapi/v2.html#ceilometer.api.controllers.v2.Statistics.max

Cheers
Date: Thu, 20 Jun 2013 15:19:44 +0530
From: jobin.rv at gmail.com
To: openstack at lists.launchpad.net

Subject: [Openstack] How to query ceilometer to get nova-specific data

Hey, all!


I installed ceilometer on Ubuntu 12.04 using the manual installation guide given here. However, I am having trouble getting data from it. When I do a ceilometer meter-list, all I get is a table with 4 rows with the names: image and image.size and its parameters; no CPU, vCPU and memory.



When I query using curl, I get some data regarding images installed and their sizes and ID and date of creation, etc.; no nova-specific data. This is how I query ceilometer using curl:

curl -X GET -H 'X-Auth-Token:<my_token_here' "http://localhost:8777/v2/resources/resource_id"



This returns a 404 Not Found error.

These are my primary concerns:

1) How do I query to get the CPU resources utilized by my virtual machines?



2) How do I decide on which port I have to pass this query? There are some documents which have v1 instead of v2 in the URL, I would like to have clarification on that too.



Thanks for your patience.
-- 






Thanks and regards,



Jobin Raju George


Third Year, Information Technology


College of Engineering Pune


Alternate e-mail: georgejr10.it at coep.ac.in










_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack at lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp 		 	   		  

_______________________________________________

Mailing list: https://launchpad.net/~openstack

Post to     : openstack at lists.launchpad.net

Unsubscribe : https://launchpad.net/~openstack

More help   : https://help.launchpad.net/ListHelp




-- 

Thanks and regards,


Jobin Raju George


Third Year, Information Technology


College of Engineering Pune


Alternate e-mail: georgejr10.it at coep.ac.in








_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack at lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130620/81a0b81a/attachment.html>