When managing a microservices environment, it’s critical for teams including developers, SREs and platform engineers to use trace data to fully understand the complexity for root cause analysis. A self-service model to actively trace and troubleshoot each service while also understanding how services interact is needed to shorten feedback loops to rapidly resolve application performance issues. Without traces, teams go blind into their production environment and incidents often involve many DevOps engineers just to establish a base understanding of what’s going on.
We’ll show you how to use OpenTelemetry automated instrumentation to add automated tracing to your microservice-based Java application.
We’ll also demonstrate how to use distributed tracing in Tanzu Observability to:
- Visualize trace data and service maps with metrics
- Trace sampling, save traces locally, and more
- Create alerts and share insights with relevant team members