A couple thoughts from a Librato founder here:<p>- Appreciate the thorough and balanced approach you took here, there&#x27;s a lot of great feedback, most of which helps validate our current roadmap and 1-2 things we&#x27;ll certainly consider.<p>- The tradeoff of providing a true utility service where you only pay for what you use is that the actual makeup of your bill can become complex (think of your AWS bill). We do pro-rate usage to the hour right now (matching AWS), so unless your metric &quot;lifetimes&quot; are sub-hour there&#x27;s shouldn&#x27;t be a huge issue.<p>- There&#x27;s a similar power&#x2F;complexity tradeoff with rollups. Unlike some solutions that only rollup via average we track multiple summary statistics e.g. min, max, sum, count, weighted average. Managing the differences between these can be confusing in some cases, so we&#x27;re currently working on a simpler interface to toggle between these. More details can be found here: <a href="https:&#x2F;&#x2F;www.librato.com&#x2F;docs&#x2F;kb&#x2F;visualize&#x2F;faq&#x2F;rollups_retention_resolution.html" rel="nofollow">https:&#x2F;&#x2F;www.librato.com&#x2F;docs&#x2F;kb&#x2F;visualize&#x2F;faq&#x2F;rollups_retent...</a><p>- Mobile support is something we&#x27;ve been incrementally adding and will continue until it&#x27;s complete e.g. the actual alerts page you land on from a notification is now mobile-ready.<p>- Tagging. In the years since we first launched (when AFAIK only OpenTSDB supported this) it&#x27;s become clear that this is becoming more and more a standard capability. Which is why we&#x27;ve been building out a next-generation data-store, which supports indexed tagging and a bunch of other new capabilities. We expect it to be in beta this summer.