Great article. We see a lot of users throwing data into VictoriaMetrics Cloud, and we try to help them by explaining what things they are not even... querying

Great article. We see a lot of users throwing data into VictoriaMetrics Cloud, and we try to help them by explaining what things they are not even... querying at all! It's true that, with great power, comes great responsibility. As I see it, I agree on that's the actual problem; and OTel adds an x factor to it, when not used wisely. Regarding the cost of ownership, tradeoffs are everywhere here. At the other side of the balance, I'd add a couple of hidden savings: in some languages I found value in just using one lib framework for instrumenting; the collector is also a great framework to unify data collection, transformation and shipping across many microservices. In the end, as the author says: there's not just one-size-fits all.