Originally posted in Obics.io We set out to build an automated incident response solution. Then we talked to more than 50 companies, and heard the same objection repeating: it won’t work on our data. The telemetry is too noisy, too low quality, too misleading. So we went digging, and found the problem underneath the problem. Logs, metrics, and traces accumulate for years, and almost nothing is ever removed. Telemetry behaves like code.

Originally posted in Obics.io If you’re not careful, logging costs can rise up to staggering amounts. Paying 5 or 10 (or more) percent of your cloud host costs for logging is just too much. And let’s be honest, most of the logs are redundant and never queried. But you still need logs just in case, otherwise, you’re blind in production next time there’s an incident. So let’s try to find a middle ground.

Originally posted in Obics.io Understanding DataDog pricing sometimes feels like you need a PhD on the matter. Some would say on purpose. And it’s a shame that such a wonderful product is accompanied by a less pleasant side. So, in this post, we’ll be demystifying exactly how DataDog bills for its log offering, which optimizations help and which don’t, and the fine-print gotchas to look out for. Plans, discounts, and overage For a big company, DataDog will always have a discounted plan, signed after careful negotiations.