# system info tab under admin

I am trying to troubleshoot why under URI /horizon/admin/info/

the service ceilometer shows as

ceilometer metering - -

rather than the IP and enabled, the ceilometer service is working and collecting data from what I have seen, sample paste below, but not enabling in horizon, which I assume is because the above.

ceilometer statistics -m image.download -p 60 +--------+---------------------+---------------------+-------+------------+------------+------------+------------+----------+----------------------------+----------------------------+ | Period | Period Start | Period End | Count | Min | Max | Sum | Avg | Duration | Duration Start | Duration End | +--------+---------------------+---------------------+-------+------------+------------+------------+------------+----------+----------------------------+----------------------------+ | 60 | 2013-11-26T03:20:14 | 2013-11-26T03:21:14 | 1 | 13147648.0 | 13147648.0 | 13147648.0 | 13147648.0 | 0.0 | 2013-11-26T03:20:14.268000 | 2013-11-26T03:20:14.268000 | +--------+---------------------+---------------------+-------+------------+------------+------------+------------+----------+----------------------------+----------------------------+

I validated the endpoints as well.

edit retag close merge delete

Sort by » oldest newest most voted

Thanks for following up! Glad you resolved the issue.

more

Ok, I'm out of ideas, sorry! Please update this 'Question' when you figure out the solution, thank you!

more

Horizon uses the output of keystone catalog in order to grab the endpoints information - does the Ceilometer / Metering output shows correctly when running this command on the command-line?

Also, note that the Ceilometer panel is called 'Resource Usage' in Horizon, and is only available for the admin in Havana.

more

output of keystone endpoint-list , I 'xxx' the IP's

+----------------------------------+-----------+--------------------------------------------+--------------------------------------------+--------------------------------------------+----------------------------------+ | id | region | publicurl | internalurl | adminurl | service_id | +----------------------------------+-----------+--------------------------------------------+--------------------------------------------+--------------------------------------------+----------------------------------+ | ec4e6b5cb3e0425b872f72e8de7c02f2 | regionOne | http://xxx.xxx.xxx.xxx:8777/ | http://xxx.xxx.xxx.xxx:8777/ | http://xxx.xxx.xxx.xxx:8777/ | 95f1193a3ebf4f688ea26ccabfa4a0ce |

+----------------------------------+---------------+----------------+----------------------------+ | id | name | type | description | +----------------------------------+---------------+----------------+----------------------------+ | 95f1193a3ebf4f688ea26ccabfa4a0ce | ceilometer | metering | Ceilometer Metering Srvice |

was there something else I needed to check on or provide for more information or detail ?

more

yes I have logged out and in and restarted the horizon services, memcached (although this one dont think matters) I had the same issue with heat and had to name it orchestration/orchestration for it to work as well.

I will play around with the naming and see if that helps, before starting with debugging the code itself.

more

No, that should be it... Did you log out of Horizon and back in again after adding the endpoint?

I also want to stress the name point - I've seen people unable to find "Heat" in Horizon because it's called "Orchestration / Stacks" - likewise the Ceilometer panel is called 'Resource Usage' and is admin-only in Havana.

more

Ok I resolved the issue, the problem was the region name, it should be RegionOne as defined by my environment variable when using keystone to create the endpoint, but for some reason keystone for THIS endpoint only did not respect that variable or changed the first character to lower

user@openstack01:~$echo$OS_REGION_NAME RegionOne

even passing the argument --os-region-name RegionOne still resulted in the endpoint being created as regionOne. it must be a keystone issue, but I will see if it's the way the service endpoint is being defined which is just as below

keystone endpoint-create --service-id=$ceilometer_svc_id --publicurl="http://$MY_IP:8777/" --internalurl="http://$MY_IP:8777/" --adminurl="http://$MY_IP:8777/"

anyway the hack is to edit the keystone database and change the endpoint table references.

more