I have been reading a lot of these comments here and some of the people who ran into issues just sound like they don&#x27;t understand what they were using or building. As many have said before opentsdb is great if you understand all of your components. Hbase is somewhat of a black art. You also truly need to understand your data. You cannot just start writing data and when it fails be upset with the product. Opentsdb is no silver bullet to the metrics game but it sure as hell is better than most at a larger scale.<p>We are doing right now roughly 1.2m&#x2F;s and will likely grow to 6-8 depending on how we chop this up. Either way you have to use any level of intelligence with this product as you do with others. I cannot stress this enough but plan out your data. Make sure you are very strict with the pattern of how things get written and the amount of tags you allow. No datapoint will initially make sense for you you may have to shift things around a bit. There is an active PR collectd that addresses metric mapping which can be very beneficial to high throughout shops.<p>Either way just make sure you know what you are getting into and understand your problem as well as your product you are choosing. Opentsdb could be overkill for people who just want a low amount of data per second. You will also need to plan retention policies &#x2F; long term storage &#x2F; hardware requirements &#x2F; etc. remember you are running hbase.