Currently 100+ physical compute hosts 1k+ vms. More being added all the time. Eventually this is going to be in the 1k's of compute nodes and and 100k+ of vm's. But right now we have been selective in allowing whats put on to give us some operational experience with OpenStack. ____________________________________________
Kris Lindgren Senior Linux Systems Engineer GoDaddy, LLC. From: matt <[email protected]<mailto:[email protected]>> Date: Monday, November 10, 2014 at 2:36 PM To: "Kris G. Lindgren" <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [Openstack-operators] Openstack telemetry stuff with monitoring my experience is that scale really matters. what is your footprint in some sort of quantified range of number of physical hosts vs vms? On Mon, Nov 10, 2014 at 4:23 PM, Kris G. Lindgren <[email protected]<mailto:[email protected]>> wrote: Hello Operators, Was wondering what you are using to gather Openstack telemetry metrics? Was looking at things around Openstack serivce api requests/s, response times (if possible), errors/s, Rabbitmq metrics, if possible pending or tasks that are in progress, ect ect. Basically your more advanced and yet basic monitoring around the openstack services. We run an ELK (elastic search, logstash, kibana) infrastructure and was wondering if anyone was a statsd/graphite output config for openstack log data -> graphite to gather some of the metrics? If not how are you currently doing it? Additionally, can anyone share what you are doing to get hypervisor health/vm statistics? We are running ceilometer, but I haven't been very happy with the results. I am also thinking something like for statsd/graphite here as well. But if you have something that works for you and can share it. Please DO!! ANYTHING is welcome. ____________________________________________ Kris Lindgren Senior Linux Systems Engineer GoDaddy, LLC. This email message and any attachment(s) hereto are intended for use only by its intended recipient(s) and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments. _______________________________________________ OpenStack-operators mailing list [email protected]<mailto:[email protected]> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
