This week on the Kubelist Podcast, we have a conversation with Ben Sigelman from LightStep about the OpenTelemetry project. This has us thinking about observability and collecting some good links we’ve been saving related to tracing, metrics, and logging using OpenTelemetry. On the podcast, Ben shares some thoughts on these “pillars of observability”.
If you are looking to up your observability game, dig in here and get started with OpenTelemetry. We tried to find the best links, but we know there are observability platforms that are integrated into OpenTelemetry that we didn’t have room to include here. This issue includes some of the best and most recent blog posts and tutorials available on OpenTelemetry.
OpenTelemetry is just a specification, so the registry and implementations are a proxy to measure how quickly it’s being adopted. The registry is where you’ll find collectors and exporters to instrument your code and view the data using the platform of your choice. Remember that OpenTelemetry is an early project, but the number of integrations in this registry show the demand and rapid adoption of this platform. 📋
Like most OpenTelemetry tutorials, this starts out with the necessary architecture explanations to make sure you know how the system is going to work. If you’re a Java developer, this is a great tutorial on how to add the OpenTelemetry dependencies into your application and get started with the auto-instrumentation capabilities of the SDK. ☕
For Go developers, don’t expect auto-instrumentation. But Liz Fong-Jones from Honeycomb has shared a great tutorial on how to instrument your Go projects with the OpenTelemetry SDK. She shows using the exporter to Honeycomb, which is a good place to start, if you don’t already have an export target. 🍯
DataDog supports and has contributed to the OpenTelemetry project. This post from their blog is a great walkthrough of what’s possible today with OpenTelemetry if you have Python and are a DataDog customer. 🐶
This is a welcome addition to a complex ecosystem. The idea of “zPages” (think healthz, metricsz, etc) is a lot simpler than setting up an external system like Zipkin or Jaeger. The internal diagnostics isn’t as powerful as dedicated systems, and isn’t where you want to end your integration efforts; however if you’re looking to get started with OpenTelemetry and add more observability to your application, this is a great way to deliver value in a few hours without needing a complex integration plan.
The folks over at NewRelic have written a detailed walk through of using OpenTelemetry to send data into NewRelic. The NewRelic user interface is mature, and for teams that already have an investment here, connecting the standards-based OpenTelemetry SDK into NewRelic One might be a perfect fit.
This marks the end of an era. Also, this is the best gif collection we’ve seen in a while.