Unlocking Observability: Your Gateway to OpenTelemetry

@jpkrohling Juraci Paixão Kröhling Software engineer @jpkrohling Unlocking Observability: Your
Gateway to OpenTelemetry

@jpkrohling @jpkrohling Juraci Paixão Kröhling Software engineer Observability OpenTelemetry Demo
Questions and answers Presenter Agenda

@jpkrohling DevOps Culture

@jpkrohling DevOps Culture Agile development Continuous integration and delivery Fast
feedback loops Change, evolution is constant Reliability

@jpkrohling Reliability Engineering

@jpkrohling Reliability engineering Resiliency Automation Error budgets, SLOs, … Launch
at scale Observability

@jpkrohling Observability

@jpkrohling O11y

@jpkrohling @jpkrohling Observability is the ability to find answers to
questions we don’t have yet.

@jpkrohling @jpkrohling Monitoring is the practice of obtaining quick answers
to frequent questions.

@jpkrohling Telemetry

@jpkrohling Telemetry data types Logs Metrics Traces Profiles Events

@jpkrohling OpenTelemetry

@jpkrohling @jpkrohling OpenTelemetry is a collection of tools, APIs, and
SDKs. Use it to instrument, generate, collect, and export telemetry data (metrics, logs, and traces) to help you analyze your software’s performance and behavior. Source: https://opentelemetry.io/

@jpkrohling Standards, specifications, and conventions Client instrumentation APIs and SDKs
Middleware

@jpkrohling @jpkrohling API Specification How the instrumentation API should look
like, no matter the SDK SDK Specification Data Specification How SDKs have to behave across languages and implementations Interface description language (IDL), specifying how data should look like and what endpoints should implement Standards and specifications

@jpkrohling Data specification OTLP OpenTelemetry Line Protocol, a set of
proto files defining both the transport and payload aspects of the telemetry data XKCD #927 Obligatory reference to XKCD #927.

@jpkrohling

@jpkrohling Data specification OTLP OpenTelemetry Line Protocol, a set of
proto files defining both the transport and payload aspects of the telemetry data XKCD #927 Obligatory reference to XKCD #927.

@jpkrohling @jpkrohling Manual instrumentation By using the instrumentation API directly
Instrumentation libraries Automatic instrumentation By using libraries that hook into well-known frameworks and libraries, such as Spring, Servlets, JAX-RS, ... Typically by doing bytecode manipulation to add instrumentation at certain interesting points Instrumentation

@jpkrohling Instrumentation demo

@jpkrohling OpenTelemetry Collector

@jpkrohling @jpkrohling Vendor-agnostic way to receive, process and export telemetry
data. Source: https://opentelemetry.io/docs/collector/

@jpkrohling OpenTelemetry Collector conceptual architecture

@jpkrohling @jpkrohling Contrib Where non-core components reside, such as vendor-specific
ones OpenTelemetry Collector - related projects Operator Kubernetes operator managing OpenTelemetry Collector instances

@jpkrohling @jpkrohling OpAMP Spec and implementation to manage collectors OpenTelemetry
Collector - related projects Builder Helper CLI tool to build OpenTelemetry Collector distributions

@jpkrohling Demo

@jpkrohling frontend Tracing lib Logging lib OTel Collector Grafana Cloud
Traces (Tempo) checkout Tracing lib Logging lib Grafana Cloud Write Path Query Path Trace context Demo architecture

@jpkrohling Key takeaways

@jpkrohling @jpkrohling Key takeaways • OpenTelemetry has different sub projects
in different areas • OpenTelemetry APIs can be used to instrument the services • Instrumentation libraries are power-ups, allowing you to quickly understand your application by understanding what your stack is doing • Automatic instrumentation, such as the ones using Java Agents, are helpful to get started quickly • The Collector can be used to make central processing of all your telemetry data and abstracting away the telemetry backends from your applications

@jpkrohling Q&A

@jpkrohling Thank you

Unlocking Observability: Your Gateway to OpenTe...

Unlocking Observability: Your Gateway to OpenTelemetry

Juraci Paixão Kröhling

More Decks by Juraci Paixão Kröhling

Other Decks in Technology

Featured

Transcript

@jpkrohling Juraci Paixão Kröhling Software engineer @jpkrohling Unlocking Observability: Your

@jpkrohling @jpkrohling Juraci Paixão Kröhling Software engineer Observability OpenTelemetry Demo

@jpkrohling DevOps Culture

@jpkrohling DevOps Culture Agile development Continuous integration and delivery Fast

@jpkrohling Reliability Engineering

@jpkrohling Reliability engineering Resiliency Automation Error budgets, SLOs, … Launch

@jpkrohling Observability

@jpkrohling O11y

@jpkrohling @jpkrohling Observability is the ability to find answers to

@jpkrohling @jpkrohling Monitoring is the practice of obtaining quick answers

@jpkrohling Telemetry

@jpkrohling Telemetry data types Logs Metrics Traces Profiles Events

@jpkrohling OpenTelemetry

@jpkrohling @jpkrohling OpenTelemetry is a collection of tools, APIs, and

@jpkrohling Standards, specifications, and conventions Client instrumentation APIs and SDKs

@jpkrohling @jpkrohling API Specification How the instrumentation API should look

@jpkrohling Data specification OTLP OpenTelemetry Line Protocol, a set of

@jpkrohling

@jpkrohling Data specification OTLP OpenTelemetry Line Protocol, a set of

@jpkrohling @jpkrohling Manual instrumentation By using the instrumentation API directly

@jpkrohling Instrumentation demo

@jpkrohling OpenTelemetry Collector

@jpkrohling @jpkrohling Vendor-agnostic way to receive, process and export telemetry

@jpkrohling OpenTelemetry Collector conceptual architecture

@jpkrohling @jpkrohling Contrib Where non-core components reside, such as vendor-specific

@jpkrohling @jpkrohling OpAMP Spec and implementation to manage collectors OpenTelemetry

@jpkrohling Demo

@jpkrohling frontend Tracing lib Logging lib OTel Collector Grafana Cloud

@jpkrohling Key takeaways

@jpkrohling @jpkrohling Key takeaways • OpenTelemetry has different sub projects

@jpkrohling Q&A

@jpkrohling Thank you