Yes, implemented it at my current company and my previous company. It's definitely worth spending the time to learn opentelemetry since its rapidly becoming the standard interface for observability signals, particularly tracing.

Roadblocks: - Some backend providers still don't support opentelemetry format. Notably the number that do support it have increased dramatically over the past year. For those who don't natively support opentelemetry, you'll likely want to use the opentelemetry collector to translate to the format of choice - There's a fair amount of difference in maturity level depending on the language you're using. For example, python's opentelemetry ecosystem is very mature whereas rust's ecosystem was lagging behind. - Tracing is probably the strongest aspect. While metrics and logs are supported, they're definitely lag behind in terms of the TLC they're given

Tidbits of note: - Opentelemetry collector has rapidly become the go-to agent of choice. It has leapfrogged vector.dev in terms of features, and I'm seeing some enterprises choose to use it as their customer-facing agent (ie GCP's agents are clearly opentelemetry + plus some extras) - As more companies support opentelemetry as a format, there's less of a need for opentelemtry's format translation feature.