<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jq on Linux Café</title>
    <link>https://mrtomlinux.org/tags/jq/</link>
    <description>Recent content in Jq on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 28 Jun 2026 09:47:47 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/jq/index.xml" rel="self" type="application/rss+xml" />
    <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>
  </channel>
</rss>
