<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Intel Clear Light";
panose-1:2 11 4 4 2 2 3 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Intel Clear Light","sans-serif"">Hi, we have been struggling with getting a meaningful set of metrics from LB stats thru ceilometer, and from a discussion about module responsibilities for providing data, an interesting
idea came up. </span><span lang="ES-AR" style="font-family:"Intel Clear Light","sans-serif"">(Thanks Pradeep!)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="ES-AR" style="font-family:"Intel Clear Light","sans-serif"">The proposal is to consolidate some kinds of metrics as pool up time (hours) and average or historic response times of VIPs and listeners, to avoid having ceilometer
querying for the state so frequently. There is a trade-off between fast response time (high sampling rate) and reasonable* amount of cumulative samples.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="ES-AR" style="font-family:"Intel Clear Light","sans-serif"">The next step in order to give more detail to the idea is to work on a use cases list to better explain / understand the benefits of this kind of data grouping.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="ES-AR" style="font-family:"Intel Clear Light","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="ES-AR" style="font-family:"Intel Clear Light","sans-serif"">What dou you think about this?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="ES-AR" style="font-family:"Intel Clear Light","sans-serif"">Do you find it will be useful to have some processed metrics on the loadbalancer side instead of the ceilometer side?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="ES-AR" style="font-family:"Intel Clear Light","sans-serif"">Do you identify any measurements about the load balancer that could not be obtained/calculated from ceilometer?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Intel Clear Light","sans-serif"">Perhaps this could be the base for other stats gathering solutions that may be under discussion?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Intel Clear Light","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="ES-AR" style="font-family:"Intel Clear Light","sans-serif"">Andres<o:p></o:p></span></p>
</div>
</body>
</html>