Observability in Java: Getting Started with OpenTelemetry
1 like482 views
The document discusses observability in Java using OpenTelemetry, outlining key concepts such as context propagation and the importance of tracing for performance monitoring. It provides guidance on setting up OpenTelemetry, including requirements and configuration steps necessary for Java applications. Additionally, it emphasizes the benefits of using OpenTelemetry for improved visibility and performance insights in distributed systems.
Observability in Java: Getting Started with OpenTelemetry
- 1. Observability in Java: Getting Started with OpenTelemetry Katy Farmer, Developer Advocate & Ted Young, Director of Open Source Development 1
- 2. 2 Hi! I’m Katy. Katy Farmer Developer Relations Manager
- 3. 3 Hi! I’m Ted. Ted Young Director of Open Source Development
- 4. Yes No No but considering it Poll: Do you currently use distributed tracing?
- 6. 6
- 7. 7 ● the ability to navigate from effect to cause Observability (n) For example… Spike in errors → misconfiguration Increased latency → new customer behavior User complaints → upstream service deployed
- 8. 8 How Did We Get Here? What Changed For Developers?
- 10. 10 SCALE!
- 11. 11 SCALE!
- 12. 12 What is a Deep System? e.g., mobile, react, client APis e.g., ingress controller e.g., custom microservices e.g., managed services like DynamoDB Independently Managed Layers
- 13. Too many tools and tool training Service dependency visibility Performance incidents Deployments Poll: What is your biggest pain point for monitoring performance?
- 14. 14 Say hi to OpenTelemetry OpenTelemetry provides a single set of APIs, libraries, agents, and collector services to capture distributed traces and metrics from your application. https://opentelemetry.io/
- 15. 15 Context Propagation Follow the transaction ● At scale, it is impossible to find the relevant data. Too much noise. ● To investigate an issue, events and metrics must first be contextualized. ○ Grouped by transaction ○ Grouped by resource ○ Grounded by product attributes ● Adding this context is a lot of work! ● OpenTelemetry does it for you. Single Transaction
- 16. Context propagation is fundamental! 16
- 18. 18 Requirements ● Java 7+ Steps ● Install OpenTelemetry ● Install Instrumentation Adapters ● Configure the SDK ● Decorate your application code Java Setup
- 19. java -javaagent:path/to/opentelemetry-auto-0.2.0.jar -Dota.exporter.jar=path/to/opentelemetry-auto-exporters-otlp-0.2.0.jar -Dota.exporter.otlp.endpoint=localhost:55678 -jar myapp.jar Java Auto Installation 19 README: https://github.com/open-telemetry/opentelemetry-auto-instr-java
- 20. Library Adapters 20 ● gRPC ● Hibernate ● HttpURLConnection ● Hystrix ● java.util.logging ● JAX-RS ● JDBC ● Jedis ● Jetty ● JMS ● JSP ● Kafka ● Lettuce ● Akka HTTP ● Apache HttpAsyncClient ● Apache HttpClient ● AWS SDK ● Cassandra Driver ● Couchbase Client ● Dropwizard Views ● Elasticsearch API ● Elasticsearch REST Client ● Finatra ● Geode Client ● Google HTTP Client ● Grizzly ● Log4j ● Logback ● MongoDB Drivers ● Netty ● OkHttp ● Play ● Play WS ● Project Reactor ● RabbitMQ Client ● Ratpack ● RMI ● RxJava ● Servlet ● Spark Web Framework ● Spring Data ● Spring Scheduling ● Spring Servlet MVC ● Spring Webflux ● Spymemcached ● Twilio Find out what’s currently available by checking the registry: https://opentelemetry.io/registry/
- 21. Warning! Lightstep does not use sampling. Leave OpenTelemetry sampling disabled. SDK Configuration 21 Propagator Options ● W3C ● B3 ● Lightstep (deprecated) Exporter Options ● Lightstep ● OTLP ● Jaeger ● Console (debug)
- 22. Span span = tracer.spanBuilder("/resource/path").setSpanKind(Span.Kind.CLIENT).startSpan(); span.setAttribute("http.method", "GET"); span.setAttribute("http.url", url.toString()); Map<String, AttributeValue> eventAttributes = new HashMap<>(); eventAttributes.put("key", AttributeValue.stringAttributeValue("value")); eventAttributes.put("result", AttributeValue.longAttributeValue(0L)); span.addEvent("Event Name", eventAttributes); Application Code 22 Further instrument your application code using the OpenTelemetry APIs: https://github.com/open- telemetry/opentelemetry-java/blob/master/QUICKSTART.md
- 24. The right observability solution ● Easily be able to see and understand your highly distributed environment ● Immediately pinpoint performance regression ● Enable developers to ship with confidence ● Enable easy sharing of information ● Keep context ● Won’t miss an insight 24
- 25. LightStep: Observability with context ● Automatic deployment and regression detection ● System and service diagrams ● Real-time and historical root cause analysis ● Correlations ● Custom alerting ● Easy Setup with no vendor lock-in ● No cardinality limitations, really 25