Hi. This is Tamimi. A developer advocate at Solace and welcomeÂ
to Tamimi’s Tidbits where we present short videos explaining technical concepts. Today we areÂ
starting a new series that talks about Distributed Tracing in Event-Driven Architecture. Let’s startÂ
with the basics and talk about Open Telemetry. Open Telemetry, or what is knownÂ
as OTEL is simply an observability framework to collect and export telemetry data. Observability is broken downÂ
into three main components: We got metrics -
and these are numericÂ
measurements such as percent CPU usage, or aggregated measurements over timeÂ
such as a count to the number of events. Logs - and you can think of this telemetry data as timestamped records which couldÂ
either be structured or unstructured. And finally traces - focuses on the big picture of what happened to an event madeÂ
by an Application, user, or API Now if we want to look at a bigger picture of theÂ
whole system, this is where Distributed Tracing comes in. It shows the
journey an event takesÂ
through multiple hops in a distributed system. This is done through a process whereÂ
the context of an event that occurred is propagated between services and processes. It is important to note that OpenTelmeteryÂ
is an industry standard and Vendor agnostic. Now that we covered the basicÂ
principles of open telemetry. Next, we will delve into how does Opentelemetery work
Comments