<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Structured-Logging on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/structured-logging/</link>
    <description>Recent content in Structured-Logging on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 20 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/structured-logging/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Logging Libraries Compared: spdlog vs logrus vs zerolog vs serilog vs winston vs logback</title>
      <link>https://www.pistack.xyz/posts/2026-06-20-logging-libraries-spdlog-logrus-zerolog-serilog-winston-logback/</link>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-20-logging-libraries-spdlog-logrus-zerolog-serilog-winston-logback/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Every application generates logs, and the logging library you choose shapes how you diagnose issues, monitor performance, and maintain your system. While cloud-based log aggregators and self-hosted observability platforms handle the collection and visualization side, the foundation starts with the logging library embedded in your application code. Choosing the right one impacts throughput, memory usage, developer experience, and integration flexibility.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
