<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Observability</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Observability feed</description>
    <item>
      <title>Kubernetes Autoscaling Demands New Observability Focus beyond Vendor Tooling</title>
      <link>https://www.infoq.com/news/2026/03/kubernetes-observability/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Observability</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/03/kubernetes-observability/en/headerimage/generatedHeaderImage-1774787835389.jpg"/&gt;&lt;p&gt;As adoption of Kubernetes autoscalers like Karpenter accelerates, a new set of platform-agnostic observability practices is emerging, shifting focus from traditional infrastructure metrics to deeper insights into provisioning behavior, scheduling latency, and cost efficiency.&lt;/p&gt; &lt;i&gt;By Craig Risi&lt;/i&gt;</description>
      <category>Kubernetes</category>
      <category>Observability</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Tue, 31 Mar 2026 12:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/03/kubernetes-observability/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Observability</guid>
      <dc:creator>Craig Risi</dc:creator>
      <dc:date>2026-03-31T12:00:00Z</dc:date>
      <dc:identifier>/news/2026/03/kubernetes-observability/en</dc:identifier>
    </item>
    <item>
      <title>Discord Engineers Add Distributed Tracing to Elixir's Actor Model without Performance Penalty</title>
      <link>https://www.infoq.com/news/2026/03/discord-elixir-actor-tracing/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Observability</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;Discord engineering detailed how they added distributed tracing to Elixir's actor model. Their custom Transport library wraps messages with trace context and uses dynamic sampling to handle million-user fanouts. CPU optimizations included skipping unsampled traces and filtering context before deserialization, recovering 10+ percentage points of overhead.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Elixir</category>
      <category>Performance</category>
      <category>Observability</category>
      <category>Distributed Systems</category>
      <category>Actor Model</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Sat, 28 Mar 2026 10:13:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/03/discord-elixir-actor-tracing/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Observability</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-03-28T10:13:00Z</dc:date>
      <dc:identifier>/news/2026/03/discord-elixir-actor-tracing/en</dc:identifier>
    </item>
  </channel>
</rss>
