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.
Please register for o11ycon+hnycon first, then register for this workshop. Conference registration is required.
Michael is a Platform Engineer at Honeycomb.io. Has worked with various public and private cloud providers over for the past 8 years. Originally was deeply rooted in system administration but has since gained fondness for infrastructure as code and developer tooling. He has been using Kubernetes + Terraform software pairing since 2017. In his spare time he is an avid PC gamer, enjoys cooking and tinkers with mixed reality.
We use cookies or similar technologies to personalize your online experience and tailor marketing to you. Many of our product features require cookies to function properly.