The problem with OpenTelemetry is that it really only good for tracing. Metrics and logs are kinda bungee strapped later: very inefficient and clunky to use.
PS: And devs (Lightspeed?) seem to really like "Open" prefix: OpenTracing + OpenCensus = OpenTelemetry.
Could you elaborate more about metrics and logs feeling bungee strapped together?
For logs it's going to necessarily be a bit messier IMO. Logs in OTel are designed to just be your existing application logs, but an SDK or agent can wrap those with a trace and span ID to correlate them for you. And so the benefit is you can bring your existing logs, but the downside is there's no clean framework to use for logging effectively, meaning there's a great deal of variability in the quality of those logs. It's also still rolling out across the languages, so while you might have excellent support in something like Java, the support in Node isn't as clean right now.
Metrics is pretty well-baked, but it's a different model and wire format than Prometheus or other systems.
My two cents about metrics: in my experience, documentation, examples, ecosystem, etc. is far behind compared to traces. OTel blogs and tutorials usually assume you want tracing only, or were written a few years back when OTel was (almost?) exclusively traces.
PS: And devs (Lightspeed?) seem to really like "Open" prefix: OpenTracing + OpenCensus = OpenTelemetry.