Book Image

Modern Distributed Tracing in .NET

By : Liudmila Molkova
Book Image

Modern Distributed Tracing in .NET

By: Liudmila Molkova

Overview of this book

As distributed systems become more complex and dynamic, their observability needs to grow to aid the development of holistic solutions for performance or usage analysis and debugging. Distributed tracing brings structure, correlation, causation, and consistency to your telemetry, thus allowing you to answer arbitrary questions about your system and creating a foundation for observability vendors to build visualizations and analytics. Modern Distributed Tracing in .NET is your comprehensive guide to observability that focuses on tracing and performance analysis using a combination of telemetry signals and diagnostic tools. You'll begin by learning how to instrument your apps automatically as well as manually in a vendor-neutral way. Next, you’ll explore how to produce useful traces and metrics for typical cloud patterns and get insights into your system and investigate functional, configurational, and performance issues. The book is filled with instrumentation examples that help you grasp how to enrich auto-generated telemetry or produce your own to get the level of detail your system needs, along with controlling your costs with sampling, aggregation, and verbosity. By the end of this book, you'll be ready to adopt and leverage tracing and other observability signals and tools and tailor them to your needs as your system evolves.
Table of Contents (23 chapters)
1
Part 1: Introducing Distributed Tracing
6
Part 2: Instrumenting .NET Applications
11
Part 3: Observability for Common Cloud Scenarios
16
Part 4: Implementing Distributed Tracing in Your Organization

Instrumenting streaming calls

So far in the book, we have covered the instrumentation of synchronous calls where the application makes a request and awaits its completion. However, it’s common to use gRPC or other protocols, such as SignalR or WebSocket, to communicate in an asynchronous way when the client and server establish a connection and then send each other messages.

Common use cases for this kind of communication include chat applications, collaboration tools, and other cases when data should flow in real time and frequently in both directions.

The call starts when the client initiates a connection and may last until the client decides to disconnect, the connection becomes idle, or some network issue happens. In practice, it means that such calls may last for days.

While a connection is alive, the client and server can write each other messages to corresponding network streams. It’s much faster and more efficient when the client and server communicate...