<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lograge on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/lograge/</link>
    <description>Recent content in Lograge on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 24 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/lograge/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Ruby Logging Libraries: Lograge vs Semantic Logger vs Ruby Logger — Complete Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-07-24-ruby-logging-libraries-lograge-semantic-logger-ruby-logger/</link>
      <pubDate>Fri, 24 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-24-ruby-logging-libraries-lograge-semantic-logger-ruby-logger/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Logging in Ruby applications starts simply — the standard library &lt;code&gt;Logger&lt;/code&gt; class gets you up and running with &lt;code&gt;logger.info(&amp;quot;Hello&amp;quot;)&lt;/code&gt;. But as your Rails application scales from a single server to a distributed system, plain-text logs become impossible to search, parse, and aggregate. Structured logging, log filtering, and asynchronous writes become essential for production observability.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
