Webinar: Logs. Traces, Metriken: Observability von .NET 7-Anwendungen

Die zunehmende Komplexität von Softwarelösungen macht ganzheitliches sammeln von Telemetriedaten unabdingbar. Technische und fachliche Telemetriedaten bieten nicht nur eine konkrete Sicht auf das Verhalten von Anwendungen und Nutzern, sie ermöglichen es uns auch, neue Funktionen oder Anpassungen zielgerichtet in den Entwicklungsprozess einfließen zu lassen um Produkte kontinuierlich besser werden zu lassen. In diesem Webinar zeigt Thorsten Hans wie Sie Ihre .NET Anwendungen mit OpenTelemetry instrumentieren um die notwendigen Insights zu bekommen.

Transcript

1. Logs, Traces, Metrics: Observability von .NET 7 Anwendungen Thorsten Hans @ThorstenHans Cloud-Native Consultant
2. Consultant @ Thinktecture #Azure #Kubernetes #Rust #CloudNative #Docker #GoLang #WebAssembly thorsten.hans@thinktecture.com thinktecture.com thorsten-hans.com @ThorstenHans Microsoft MVP | Docker Captain Thorsten Hans
3. • Introduction • OpenTelemetry • Instrumenting .NET Apps • Conclusion Agenda
4. • Introduction • OpenTelemetry • Instrumenting .NET Apps • Conclusion Agenda
5. With Observability, we gain insights into complex systems by monitoring their states and behaviors. Introduction What is Observability?
6. Addressing Observability means we must collect, store, and analyze data from different sources (e.g., individual apps, databases, caches, infrastructure, …) Introduction What is Observability?
7. With Observability we can identify problems and potential defects before they happen, because we look at data over a period of time, which allows us to spot trends Introduction What is Observability?
8. • Logs • Textual records of discrete events or actions within a system • Provides a chronological record that aids in root cause analysis and debugging • Metrics • Point in time measure of different sources • Enables monitoring and alerting based on predefined thresholds or anomalies • Traces • Collection of spans that outline a program’s flow and data progression • Enables end-to-end tracing and troubleshooting of distributed systems Introduction Observability data types
9. • Introduction • OpenTelemetry • Instrumenting .NET Apps • Conclusion Agenda
10. • OpenTelemetry (OTel) is an open-source observability framework • OTel empowers devs with generating, collecting, and exporting telemetry data from distributed systems. • OTel provides a standardized set of APIs, libraries, and instrumentation tools that we can use to instrument our apps • OTel supports many programming languages and integrates with various observability systems OpenTelemetry https://opentelemetry.io/
11. • Introduction • OpenTelemetry • Instrumenting .NET Apps • Conclusion Agenda 1
12. Instrumenting .NET Apps • Let’s instrument a regular .NET Web App Demo
13. • Add Instrumentation packages to collect more insights • Exporter packages are used to send / expose data to integrate with well-known, battle-tested observability solutions (Jaeger, Zipkin, Prometheus, Elastic, ….) • Individual metrics and spans are captured using regular types from .NET BCL Instrumenting .NET Apps
14. Instrumenting .NET Apps • Take our instrumentation to the next level Demo
15. • Introduction • OpenTelemetry • Instrumenting .NET Apps • Conclusion Agenda
16. • Observability is mission-critical to • Maintain the reliability and performance of your app • Visualize the health of your app • Gain insights about how users use your app • Collect data and generate KPIs and group them into meaningful dashboards • Observability is more than just using ILogger<T> • Do not underrate the importance of custom metrics Conclusion
17. • OpenTelemetry is the de-facto standard • Both manual and automatic instrumentation are super helpful to get insights of the entire application • Look for dedicated Instrumentation NuGet packages to gain more insights e.g, • OpenTelemetry.Instrumentation.SqlClient • OpenTelemetry.Instrumentation.GrpcNetClient • OpenTelemetry.Instrumentation.StackExchangeRedis • OpenTelemetry.Instrumentation.EntityFrameworkCore Conclusion
18. Thanks for your attention @ThorstenHans