Learn the value that OpenTelemetry can bring to organizations that aim to implement observability best practices, and gain a deeper understanding of how different building blocks interact with each other to bring out-of-the-box, vendor-neutral instrumentation to your stack. With examples in Java, this book shows how to use OpenTelemetry APIs and configure plugins and SDKs to instrument services and produce valuable telemetry data. You’ll learn how to maximize adoption of OpenTelemetry and encourage the change needed in debugging workflows to reduce cognitive load for engineers troubleshooting production workloads. Adopting observability best practices across an organization is challenging. This book begins with a discussion of how operational monitoring processes widely followed for decades fall short at providing the insights needed for debugging cloud-native, distributed systems in production. The book goes on to show how the Cloud Native Computing Foundation’s OpenTelemetry project helps you standardize instrumentation and transport of telemetry signals, providing a common language for all observability tooling.
You Will Learn: Why observability is a necessity in modern distributed systems The value of OpenTelemetry for engineers and organizations OpenTelemetry component specification and general design Tracing, metrics, and logs APIs and SDKs, with examples in Java OpenTelemetry Collectors and recommended transport and processing pipelines How to adopt observability standards across an organization
Who This Book Is For: Software engineers familiar with cloud-native technologies and operational monitoring who want to instrument and export telemetry data from their services; observability leads who want to roll out OpenTelemetry standards and best practices across their organizations; and Java developers who want a book with OpenTelemetry examples in that language
Dan is a Principal Engineer at Skyscanner, leading their observability transformation to ensure travellers get a reliable and performant experience when booking their next holiday. He’s a big advocate of open standards and CNCF projects like OpenTelemetry to back the instrumentation and collection of telemetry data. He has worked both in big and small companies and institutions, from CERN to SKIPJAQ, always building software and infrastructure to reduce the cognitive load associated with supporting production services.
A lot more about the benefits of tracing and auto-instrumentation than I expected. I like the last part with practical advice about introducing and working with OpenTelemetry in practice and I have similar experiences.
I’ve picked some good practices about configuring OTel Collectors as well.
In my experience traces are really important, but it was too much at some point. In theory they can help you with publishing less logs or metrics, but in practice how many teams will be willing to relay only on heavily sampled traces? Even if you do use traces a lot I would rather want to make sure that metrics and logs reflect all the requests as sometimes you do really need to investigate what one particular customer did in the system.
I don’t have a strong opinion about auto-instrumentation yet. On one hand I get the convenience, but on the other there seems to be a lot of „magic” in that.
La verdad no sé si el tema de opentelemetry es muy complejo, pero sentí que el autor brincó muy rápido a temas prácticos antes de explicar a fondo que es OTel, los componentes, de que se trata cada uno, y así Tal vez fue breve pero hubieron esos conceptos que no estoy seguro aún de ellos. Sin embargo, no es un mal libro pues explica muchos de los temas ya más programáticos en amplitud. Creo que es un libro para personas con más experiencia y en especial orientados a java. Buscaré más libros en el tema