<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>Hell allo,</div>
<div><br>
</div>
<div>Coming back around to this. I re-did our logstash.conf that we shared out ~7months ago [1] to now do deeper parsing of wgsi logs from: Nova, neutron, keystone, glance and nova-metadata services. In our config we also have logstash outputting timing metrics
(response time and number of request) to statsd, which is then stored in graphite. I have included a kibana dashboard that is specific to just the API requests [2]. I have also included a grafana dashboard [3] for the graphite outputs. This dashboard breaks
out response time to upper/mean values for each service via get/post/delete ect ect and http status code (200-500). This should let you see max/mean api response times for each service as well as get a count on the number of API requests during a time interval.</div>
<div><br>
</div>
<div>[1] https://github.com/godaddy/openstack-logstash</div>
<div>[2] <a href="https://github.com/godaddy/openstack-logstash/blob/master/API-Stats.json">https://github.com/godaddy/openstack-logstash/blob/master/API-Stats.json</a></div>
<div>[3] <a href="https://github.com/godaddy/openstack-logstash/blob/master/grafana.json">https://github.com/godaddy/openstack-logstash/blob/master/grafana.json</a></div>
<div><br>
</div>
<div>If you use this and have some comments/improvements – please feel free to send a pull request and/or contact me or Mike Dorman directly.</div>
<div><br>
</div>
<div>We also ended up using diamond to gather compute node statistics along with per vm stats running on each compute node.</div>
<div>
<div>
<div>____________________________________________</div>
<div> </div>
<div>Kris Lindgren</div>
<div>Senior Linux Systems Engineer</div>
<div>GoDaddy, LLC.</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<br>
</div>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Nov 10, 2014 at 10:23 PM, Kris G. Lindgren <span dir="ltr">
<<a href="mailto:klindgren@godaddy.com" target="_blank">klindgren@godaddy.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>
<div>
<div>Hello Operators,</div>
<div><br>
</div>
<div>Was wondering what you are using to gather Openstack telemetry metrics?</div>
<div><br>
</div>
<div>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?</div>
<div><br>
</div>
<div>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.</div>
<div>
<div>
<div>____________________________________________</div>
<div> </div>
<div>Kris Lindgren</div>
<div>Senior Linux Systems Engineer</div>
<div>GoDaddy, LLC.</div>
<div><br>
</div>
<div>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.</div>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>