<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Otel on Brian Mehrman</title>
    <link>https://www.brianmehrman.com/tags/otel/</link>
    <description>Recent content in Otel on Brian Mehrman</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 16 May 2026 14:48:41 -0500</lastBuildDate>
    <atom:link href="https://www.brianmehrman.com/tags/otel/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Observability Locally With Grafana</title>
      <link>https://www.brianmehrman.com/blog/observability-locally-with-grafana/</link>
      <pubDate>Sat, 16 May 2026 14:48:41 -0500</pubDate>
      <guid>https://www.brianmehrman.com/blog/observability-locally-with-grafana/</guid>
      <description>&lt;p&gt;When programming you need to know what is happening inside that function or method.
You need to reproduce a bug or you are debugging a performance issue.
Most of the time adding a trace statement is enough.&lt;/p&gt;
&lt;p&gt;When debugging production, you&amp;rsquo;re not going to find the answer with a trace message on a remove server.
At some point your app gets complicated enough that you need to see what&amp;rsquo;s
actually happening — not guess. That&amp;rsquo;s where observability comes in.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
