Per-host is also not well-suited for elastic computing. Pricing should be billed for host-hours instead, if you ask me. I'm familiar with zipkin, but it's an ov

Per-host is also not well-suited for elastic computing. Pricing should be billed for host-hours instead, if you ask me. I'm familiar with zipkin, but it's an overkill for most projects; Etsy CrossStitch - although I follow Etsy's projects, I don't think I've seen it. Anyway, I think I've exchanges comments with you before in here, but the issue is that you guys have some large enterprise clients, and usually with companies like yours, pricing totally gets shifted towards that model. It's really too expensive to pay more for monitoring (although I greatly value the data), when it exceeds the cost of the server itself. At least, business people can hardly justify something with clear costs like hardware (cloud or not) to something without 100% clear benefit to them (as they don't use it; it's for the developers, who's job should be to write code that just works and doesn't require all these expensive babysitting tools, if you see my point). This is not to attack you or anything, but my experiences across multiple organizations. Worst case (at least with your competitor New Relic) is that you pay for internal dev servers as well. Come on, give me a break - how can you compare live with dev servers, really? This is the abuse that I'm talking about. Maybe it's a different situation with you, I don't know, but it's really unfair and a frustration for us.