June 9 2021 10:15 am June 9 2021 10:45 am America/Los_Angeles OpenTelemetry vs Proprietary Libraries You've likely heard about or are using OpenTelemetry; the open-source project that helps you generate application telemetry in vendor-neutral ways. Or, perhaps you're using a vendor-specific instrumentation library (for example, Honeycomb's Beelines). Maybe you're trying to decide which to use... Virtual Meet
TRACK 4: Open-Spaces
Wednesday, June 9 2021 10:15 am - 10:45 am PT

OpenTelemetry vs Proprietary Libraries

You've likely heard about or are using OpenTelemetry; the open-source project that helps you generate application telemetry in vendor-neutral ways. Or, perhaps you're using a vendor-specific instrumentation library (for example, Honeycomb's Beelines). Maybe you're trying to decide which to use. What are the tradeoffs? What is there to know? As an open standard, OpenTelemetry has support and investment from many different vendors and it offers benefits like advanced auto-instrumentation, cross-compatibility across many vendor products, and potential to have native support across libraries and ecosystems. However, as with any open standard, it is designed to serve a broad range of use cases; meaning that it may not reach the same level of fine-tuning and customization as vendor-specific instrumentation libraries. This open space is to hear about your experiences. Have you used OTEL? What worked well, what didn't? Have you tried both OTEL and vendor-specific libraries? If so, what factored into that choice and how did it go? Are there concerns you have about OTEL that instead steer you toward proprietary libraries? This discussion is all about sharing adoption experiences and unpacking the pros and cons.