.NET Diagnostics for Applications: Best Practices
Issues in deployed applications can be difficult to diagnose. This course will teach you how to use capabilities in .NET to trace and instrument your applications in order to log the behavior of the system and diagnose problems.
What you'll learn
Software doesn’t always behave as expected. When problems occur, you need to understand the behavior of the deployed system in order to diagnose and solve issues with your code and data. In this course, .NET Diagnostics for Applications: Best Practices, you’ll learn to how to instrument and trace your code, in order to create useful diagnostics. First, you’ll learn how to instrument apps using classes in System.Diagnostics, like Debug, TraceSource, and DiagnosticSource. Next, you’ll discover the various destinations for TraceListeners and Logging Providers. Finally, you’ll explore how to instrument more complex, distributed applications using the Activity class and OpenTelemetry. When you’re finished with this course, you’ll have the skills and knowledge of instrumenting and tracing needed to implement diagnostics for .NET applications.
Table of contents
- Understanding Diagnostics in Applications 7m
- Logging Considerations 8m
- Diagnostics in .NET 7m
- Exploring the System.Diagnostics Namespace 2m
- Using Debug and Assert 6m
- Instrumenting Code with TraceSource 9m
- Listening for DiagnosticSource Events 7m
- Instrumenting Code Using DiagnosticSource 3m
- Understanding EventSource 3m
- Capturing EventSource Events 5m
- Instrumenting Code Using EventSource 4m
- The ILogger API 4m
- Understanding Distributed Tracing 6m
- System.Diagnostics.Activity 7m
- Instrumenting Apps Using System.Diagnostics.Activity 5m
- Correlating Trace IDs across Processes 6m
- Demo: Tracing across Web APIs 5m
- Understanding OpenTelemetry 4m
- Collecting Trace Data with OpenTelemetry 9m
- Installing Zipkin 2m
- Exporting and Viewing Trace Data across Distributed Systems 5m
- Course Summary 1m