<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Observability on Daniel Monteiro&#39;s blog</title>
    <link>https://dfamonteiro.com/tags/observability/</link>
    <description>Recent content in Observability on Daniel Monteiro&#39;s blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 19:36:49 +0100</lastBuildDate>
    <atom:link href="https://dfamonteiro.com/tags/observability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>One observability metric to rule them all</title>
      <link>https://dfamonteiro.com/posts/one-observability-metric/</link>
      <pubDate>Sun, 04 Oct 2026 19:36:49 +0100</pubDate>
      <guid>https://dfamonteiro.com/posts/one-observability-metric/</guid>
      <description>&lt;p&gt;I was talking with some colleagues regarding their &lt;a href=&#34;https://dfamonteiro.com/posts/production-load-generator/&#34; &gt;load-testing&lt;/a&gt; efforts, when an interesting question came up during the conversation:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;How do we determine which services deserve the most optimization engineering effort?&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&lt;/blockquote&gt;&#xA;&lt;p&gt;To solve this riddle, we need a source of performance data: server logs, traces, etc - thankfully, the product I work on has OpenTelemetry support and therefore we have reams of observability data stored in ClickHouse, so it&amp;rsquo;s really a matter of crafting the right query. But which one?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
