<p>-----Original Message-----<br/>From: Thierry Carrez <<a href="mailto:thierry@openstack.org">thierry@</a><a href="mailto:thierry@openstack.org">openstack.org</a>><br/>To: <a href="mailto:openstack@lists.launchpad.net">openstack</a><a href="mailto:openstack@lists.launchpad.net">@</a><a href="mailto:openstack@lists.launchpad.net">lists.launchpad.net</a><br/>Sent: Fri, 04 May <a href="tel:20122">2012 2</a>:50<br/>Subject: Re: [Openstack] [Metering] schema and counter definitions<br/><br/>Robert Collins wrote:<br/>> On Fri, May 4, 2012 at 5:27 AM, Turner, Whit (Cloud Services)<br/>> <<a href="mailto:Whit.Turner@hp.com">Whit.Turner</a><a href="mailto:Whit.Turner@hp.com">@</a><a href="mailto:Whit.Turner@hp.com">hp.com</a>> wrote:<br/>>> Hi - I think a flexible aggregation scheme is needed; the levels of<br/>>> aggregation available should be definable in the meter independent of the<br/>>> sources of usage data themselves. If invoices need to be very granular down<br/>>> to the lowest possible level, then this drives higher data requirements all<br/>>> through the processing chain, including the rating engine. Traditional<br/>>> systems tend to pass less granular (more highly aggregated) data into the<br/>>> rating engine so that bill runs and invoices can be generated efficiently.<br/>>> At cloud-scale, this can be problematic. Given some “big data” approaches,<br/>>> though, this could be handled in a more granular and real-time fashion.<br/>> <br/>> Has anyone looked at what statsd does? It has very similar<br/>> requirements (simple to use, no hard a-priori definition of things to<br/>> count, a few base types to track), and needs to be horizontally<br/>> scalable.<br/><br/>Also Swift has plans to use statsd for instrumentation/monitoring, so<br/>it's definitely worth a look to see if it could be used here as well.<br/><br/><a href="http://folsomdesignsummit2012.sched.org/event/d9135eabdd775432c74c3f1d32a325d3">http://</a><a href="http://folsomdesignsummit2012.sched.org/event/d9135eabdd775432c74c3f1d32a325d3">folsomdesignsummit2012</a><a href="http://folsomdesignsummit2012.sched.org/event/d9135eabdd775432c74c3f1d32a325d3">.</a><a href="http://folsomdesignsummit2012.sched.org/event/d9135eabdd775432c74c3f1d32a325d3">sched.org</a><a href="http://folsomdesignsummit2012.sched.org/event/d9135eabdd775432c74c3f1d32a325d3">/</a><a href="http://folsomdesignsummit2012.sched.org/event/d9135eabdd775432c74c3f1d32a325d3">event</a><a href="http://folsomdesignsummit2012.sched.org/event/d9135eabdd775432c74c3f1d32a325d3">/d9135eabdd775432c74c3f1d32a325d3</a><br/><a href="http://etherpad.openstack.org/FolsomSwiftStatsd">http://</a><a href="http://etherpad.openstack.org/FolsomSwiftStatsd">etherpad.openstack.org</a><a href="http://etherpad.openstack.org/FolsomSwiftStatsd">/</a><a href="http://etherpad.openstack.org/FolsomSwiftStatsd">FolsomSwiftStatsd</a><br/><br/>-- <br/>Thierry Carrez (ttx)<br/>Release Manager, OpenStack<br/><br/>_______________________________________________<br/>Mailing list: <a href="https://launchpad.net/~openstack">https://</a><a href="https://launchpad.net/~openstack">launchpad.net</a><a href="https://launchpad.net/~openstack">/~</a><a href="https://launchpad.net/~openstack">openstack</a><br/>Post to     : <a href="mailto:openstack@lists.launchpad.net">openstack</a><a href="mailto:openstack@lists.launchpad.net">@</a><a href="mailto:openstack@lists.launchpad.net">lists.launchpad.net</a><br/>Unsubscribe : <a href="https://launchpad.net/~openstack">https://</a><a href="https://launchpad.net/~openstack">launchpad.net</a><a href="https://launchpad.net/~openstack">/~</a><a href="https://launchpad.net/~openstack">openstack</a><br/>More help   : <a href="https://help.launchpad.net/ListHelp">https://</a><a href="https://help.launchpad.net/ListHelp">help.launchpad.net</a><a href="https://help.launchpad.net/ListHelp">/</a><a href="https://help.launchpad.net/ListHelp">ListHelp</a><br/><br/></p>