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

Managing logging costs

Similarly to tracing and metrics, logging increases the compute resources needed to run an application, the cost of running a logging pipeline (if any), and the costs associated with using (or running) an observability backend. Vendor pricing is frequently based on a combination of telemetry volume, retention time, and API calls, including queries.

We already know how to write logs efficiently, so let’s talk about pipelines and backends.

Pipelines

A logging pipeline consists of the infrastructure needed to send logs to the backend of your choice. It’s typical to do some grokking, parsing, transformations, buffering, throttling, and hardening on the way to the backend.

In a simple case, it’s all done by your vendor’s logging provider or the OpenTelemetry processors and exporter inside the process.

In many cases, we need logging pipelines to capture logs and events coming from outside – the OS, self-hosted third...