The alternative is vendor lockin, $$$, and spotty support for complex environments with zero chance of ever getting 100% coverage.<p>At least with Open Telemetry, anyone can write an OTLP "source" using free, open specifications, and it'll "just work" with dozens of third-party "sinks". That's <i>huge!</i><p>Sure, there's a lot of experimental tags on semantic conventions, but at the end of the day, that's not that critical. It's <i>just</i> data: most sinks don't "interpret" these tags, they just display them as-is, so changes aren't breaking changes.
The alternative is Prometheus (which is freaking great) and Jaegar (which is freaking great), each <i>alone</i>. This is better, because Otel is trying to put two distinct things (monitoring and metrics, distributed tracing) into one package, because they know how to use neither.<p>Neither Prometheus metrics nor Jaeger traces are magic bullets. Neither of them are <i>complicated</i>, either, and in fact the fact that they're not complicated is their greatest strength. You can and should understand every facet of what they entail. You should build the (very small) shims that they need for your company's framework every time. It's not hard. It's not hard because it's not complicated. The fact that it's not complicated seems to break people's brains. They are accurate because they're simple and they're easy to work with because they're simple, and OTel is neither.