<?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 Linux Café</title>
    <link>https://mrtomlinux.org/tags/logging/</link>
    <description>Recent content in Logging on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 11 Jul 2026 08:25:55 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/logging/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Container Logs with Podman and systemd-journald</title>
      <link>https://mrtomlinux.org/post/2026-07-11-taming-container-logs-with-podman-and-systemd/</link>
      <pubDate>Sat, 11 Jul 2026 08:25:55 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-07-11-taming-container-logs-with-podman-and-systemd/</guid>
      <description>&lt;h2 id=&#34;introduction-to-container-logs&#34;&gt;Introduction to Container Logs&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been running a homelab with various self-hosted services for a while now, and managing container logs has been a challenge. With containerization making it easy to spin up multiple containers, keeping track of their logs can be overwhelming. In my experience, using Podman and systemd-journald has been a game-changer for taming container logs.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-are-container-logs&#34;&gt;What are Container Logs?&lt;/h2&gt;&#xA;&lt;p&gt;Container logs are essentially the output of a container&amp;rsquo;s stdout and stderr streams. They contain valuable information about the container&amp;rsquo;s execution, such as errors, warnings, and debug messages. By default, container logs are stored in the container&amp;rsquo;s filesystem, which can lead to log rotation issues and make it difficult to manage logs across multiple containers. I&amp;rsquo;ve seen this go wrong when logs start filling up the container&amp;rsquo;s disk space, causing all sorts of issues.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Taming journalctl: Tips for Filtering Out Noise and Finding Useful Error Messages in Your System Logs</title>
      <link>https://mrtomlinux.org/post/2026-07-01-taming-journalctl-tips-for-filtering-out-nois/</link>
      <pubDate>Wed, 01 Jul 2026 09:40:00 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-07-01-taming-journalctl-tips-for-filtering-out-nois/</guid>
      <description>&lt;h2 id=&#34;introduction-to-journalctl&#34;&gt;Introduction to journalctl&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been using Linux for years, and &lt;code&gt;journalctl&lt;/code&gt; has become an essential tool in my daily workflow. If you&amp;rsquo;re like me, you&amp;rsquo;re probably familiar with the &lt;code&gt;journalctl&lt;/code&gt; command, which is used to query and display logs from systemd&amp;rsquo;s journal. However, with the vast amount of data that&amp;rsquo;s logged, it can be overwhelming to sift through and find the information you need. In this article, I&amp;rsquo;ll share some practical tips and tricks for filtering out noise and finding useful error messages in your system logs using &lt;code&gt;journalctl&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Taming Log Noise with jq and yq: Extracting Insights from Messy JSON and YAML Logs</title>
      <link>https://mrtomlinux.org/post/2026-06-28-taming-log-noise-with-jq-and-yq-extracting-in/</link>
      <pubDate>Sun, 28 Jun 2026 09:47:47 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-06-28-taming-log-noise-with-jq-and-yq-extracting-in/</guid>
      <description>&lt;h2 id=&#34;introduction-to-log-noise&#34;&gt;Introduction to Log Noise&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve spent countless hours digging through log files to troubleshoot issues or monitor system performance. But let&amp;rsquo;s be real, log noise can quickly become overwhelming. I&amp;rsquo;ve seen this go wrong when you&amp;rsquo;re dealing with massive log files and no clear way to extract valuable insights. Recently, I&amp;rsquo;ve been working with increasingly complex JSON and YAML logs, which led me to explore tools like &lt;code&gt;jq&lt;/code&gt; and &lt;code&gt;yq&lt;/code&gt; to tame the noise. Don&amp;rsquo;t bother with trying to parse these logs manually - it&amp;rsquo;s a recipe for disaster.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Taming Log Noise with jq and yq: Extracting Insights from Messy JSON and YAML Logs</title>
      <link>https://mrtomlinux.org/post/2026-06-14-taming-log-noise-with-jq-and-yq-extracting-in/</link>
      <pubDate>Sun, 14 Jun 2026 08:17:40 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-06-14-taming-log-noise-with-jq-and-yq-extracting-in/</guid>
      <description>&lt;h2 id=&#34;introduction-to-log-noise&#34;&gt;Introduction to Log Noise&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen log files become increasingly cluttered over the years, making it tough to find the information I need. With the complexity of modern systems, log noise has become a significant problem. Log noise refers to the unnecessary or redundant information in log files that can make it difficult to extract valuable insights. In this article, I&amp;rsquo;ll explore how to tame log noise using &lt;code&gt;jq&lt;/code&gt; and &lt;code&gt;yq&lt;/code&gt;, two powerful command-line tools for parsing JSON and YAML data.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Taming Duplicate Logs with uniq, sort, and a Dash of jq</title>
      <link>https://mrtomlinux.org/post/2026-05-18-taming-duplicate-logs-with-uniq-sort-and-a-da/</link>
      <pubDate>Mon, 18 May 2026 10:31:59 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-05-18-taming-duplicate-logs-with-uniq-sort-and-a-da/</guid>
      <description>&lt;h2 id=&#34;introduction-to-log-management&#34;&gt;Introduction to Log Management&lt;/h2&gt;&#xA;&lt;p&gt;As a Linux user, you&amp;rsquo;re probably familiar with the importance of logs. I&amp;rsquo;ve seen this go wrong when trying to debug an issue or monitor system performance - duplicate logs can be overwhelming. In this article, we&amp;rsquo;ll explore how to remove duplicates using &lt;code&gt;uniq&lt;/code&gt;, &lt;code&gt;sort&lt;/code&gt;, and &lt;code&gt;jq&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understanding-the-problem&#34;&gt;Understanding the Problem&lt;/h2&gt;&#xA;&lt;p&gt;Duplicate logs can come from multiple sources: multiple instances of the same service, redundant logging mechanisms, or simple configuration mistakes. The real trick is to identify the cause and develop a strategy for removing duplicates. Don&amp;rsquo;t bother with trying to manually sift through logs - that&amp;rsquo;s a surefire way to waste time and miss important trends.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Introduction to the Elastic Stack</title>
      <link>https://mrtomlinux.org/post/elasticstack/</link>
      <pubDate>Wed, 15 Jan 2025 00:00:00 +0000</pubDate>
      <guid>https://mrtomlinux.org/post/elasticstack/</guid>
      <description>&lt;p&gt;The &lt;strong&gt;Elastic Stack&lt;/strong&gt;, commonly referred to as the &lt;strong&gt;ELK Stack&lt;/strong&gt;, is a suite of open-source tools designed for search, logging, and analytics. The stack consists of &lt;strong&gt;Elasticsearch&lt;/strong&gt;, &lt;strong&gt;Logstash&lt;/strong&gt;, &lt;strong&gt;Kibana&lt;/strong&gt;, and (later additions like) &lt;strong&gt;Beats&lt;/strong&gt;, providing a comprehensive solution for collecting, storing, analyzing, and visualizing data.&lt;/p&gt;&#xA;&lt;p&gt;Whether you’re building a search engine, monitoring infrastructure logs, or analyzing security events, the Elastic Stack offers a flexible and scalable platform for handling data at scale. This post explores the key components, features, and use cases of the Elastic Stack.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Understanding Rsyslog</title>
      <link>https://mrtomlinux.org/post/rsyslog/</link>
      <pubDate>Sat, 26 Oct 2024 00:00:00 +0000</pubDate>
      <guid>https://mrtomlinux.org/post/rsyslog/</guid>
      <description>&lt;p&gt;In Linux, system logs are essential for monitoring performance, troubleshooting issues, and maintaining security. &lt;code&gt;rsyslog&lt;/code&gt; is a powerful and flexible logging system widely used in modern Linux distributions. It offers high performance, advanced filtering, and support for various output formats, making it a valuable tool for managing logs effectively.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-rsyslog&#34;&gt;What is Rsyslog?&lt;/h2&gt;&#xA;&lt;p&gt;&lt;code&gt;rsyslog&lt;/code&gt; stands for &amp;ldquo;Rocket-fast System Logging.&amp;rdquo; It is an enhanced version of the traditional &lt;code&gt;syslog&lt;/code&gt; system, designed to handle high-speed log processing while offering advanced capabilities like:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
