Ronak Banka TRACING MATTERS! devopsdays.org/singapore | @devopsdaysSG

HOW TRACING WORKS & DEMO WHAT IS DISTRIBUTED TRACING? WHY DISTRIBUTED TRACING? 01 02 AGENDA 03

WHY DISTRIBUTED TRACING?

LACK OF VISIBILITY!

WHY HAPPENED? • Users are Scaling at a Rapid Speed. • Engineering Organizations are Scaling to Ship Business Value Faster • Monoliths are getting transformed to Microservices

MICROSERVICES ARCHITECTURE CAN GET VERY COMPLEX!

With More Complexity, comes more Failure Scenarios!

No content

BUT We have Monitoring in Place!! WHY Do we even need Tracing based Observability?

Monitoring is about what we Already Know, Observability is about Answering questions!

● If a request failed, where did the errors happen? ● If there is latency in the app, where are the bottlenecks? ● When Processing a request, which all other services are involved and what they did? ● Performance Behaviors ● Root Cause Analysis in case of an Incident? Distributed Tracing can Answer

WHAT IS DISTRIBUTED TRACING?

Distributed tracing refers to methods of observing requests as they propagate through distributed systems It is also a diagnostic technique that reveals how a set of services coordinate to handle individual user requests.

• Trace represents an end-to-end request; made up of single or multiple spans • Span represents work done by a single-service with time intervals and associated metadata; the building blocks of a trace • Tags metadata to help contextualize a span CONCEPTS OF TRACING?

● Trace Identifier: trace_id is generated in the root span and is immutable. ● Parent Identifier: span_id of the parent span that spawned the current operation HOW ARE TRACES CONNECTED? Source: https://blog.sentry.io/distributed-tracing-101-for-full-stack-

Various Tracing Tools

No content

Confidential and proprietary. © Temus Pte Ltd 2022 22 Service Map

Confidential and proprietary. © Temus Pte Ltd 2022 24 Traces

Confidential and proprietary. © Temus Pte Ltd 2022 25 Metrics