<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jaeger on DevOps Engineer &amp; CloudAdmin</title><link>https://ru-admin.github.io/tags/jaeger/</link><description>Recent content in Jaeger on DevOps Engineer &amp; CloudAdmin</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><atom:link href="https://ru-admin.github.io/tags/jaeger/index.xml" rel="self" type="application/rss+xml"/><item><title>.NET Backend Observability &amp; Telemetry Integration</title><link>https://ru-admin.github.io/posts/sre-observability/dotnet-telemetry-observability/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ru-admin.github.io/posts/sre-observability/dotnet-telemetry-observability/</guid><description>&lt;h2 id="net-backend-observability-telemetry-integration--performance-optimization"&gt;.NET Backend Observability: Telemetry Integration &amp;amp; Performance Optimization&lt;/h2&gt;
&lt;hr&gt;
&lt;h4 id="client"&gt;Client&lt;/h4&gt;
&lt;p&gt;E-commerce platform with high-load .NET 8 backend&lt;/p&gt;
&lt;hr&gt;
&lt;h4 id="challenge"&gt;Challenge&lt;/h4&gt;
&lt;p&gt;The .NET backend had no observability — no distributed tracing, no centralized metrics, no structured logging. Finding slow requests required manual log digging. The team needed full OpenTelemetry integration: trace propagation from Ingress through .NET to downstream services (PostgreSQL, Redis, RabbitMQ, HTTP upstreams), automatic slow-query detection, and a path to optimize P99 latency.&lt;/p&gt;</description></item></channel></rss>