<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Logging on Nalar</title>
    <link>https://nalar.dev/tags/logging/</link>
    <description>Recent content in Logging on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/logging/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Structured Logging in Go with slog</title>
      <link>https://nalar.dev/structured-logging-go-slog/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/structured-logging-go-slog/</guid>
      <description>&lt;p&gt;Plain text logs are easy to print but difficult to query reliably. Once an application runs across multiple processes or containers, operators usually need to filter events by fields such as HTTP status, request path, customer ID, or latency rather than search arbitrary strings.&lt;/p&gt;&#xA;&lt;p&gt;Go&amp;rsquo;s standard library includes &lt;code&gt;log/slog&lt;/code&gt; for structured logging. It was added in Go 1.21, so the examples in this article require Go 1.21 or newer.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-structured-logging-changes&#34;&gt;What structured logging changes&lt;/h2&gt;&#xA;&lt;p&gt;A traditional log message often embeds data inside prose:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
