<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Opentelemetry on Danilo Falcão da Silva</title><link>https://falcao.org/tags/opentelemetry/</link><description>Recent content in Opentelemetry on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 21 Jun 2026 23:32:26 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/opentelemetry/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenTelemetry Collector: The Observability Pipe You’re Going To Be On-Call For</title><link>https://falcao.org/posts/opentelemetry-collector-observability-pipe-on-call/</link><pubDate>Sun, 21 Jun 2026 23:32:26 -0300</pubDate><guid>https://falcao.org/posts/opentelemetry-collector-observability-pipe-on-call/</guid><description>&lt;p>The pager goes off because the app is sick. You start the usual dance: open the traces, pull the logs, check the deploy timeline. Except the traces are thin, the logs are lagging by four minutes, and the dashboards that should be screaming are politely flat. For a second you wonder if the incident is actually over. It isn&amp;rsquo;t. Your telemetry pipeline is the thing that&amp;rsquo;s down, and it&amp;rsquo;s been quietly dropping spans since the memory pressure started — which is exactly when you needed it most.&lt;/p></description></item></channel></rss>