<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Json on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/json/</link>
    <description>Recent content in Json on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 16 Jul 2026 09:18:34 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/json/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Log Noise with jq: Extracting Insights from JSON Logs in Linux</title>
      <link>https://linuxeries.org/post/2026-07-16-taming-log-noise-with-jq-extracting-insights-/</link>
      <pubDate>Thu, 16 Jul 2026 09:18:34 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-07-16-taming-log-noise-with-jq-extracting-insights-/</guid>
      <description>&lt;h2 id=&#34;introduction-to-log-noise-and-jq&#34;&gt;Introduction to Log Noise and jq&lt;/h2&gt;&#xA;&lt;p&gt;As someone who&amp;rsquo;s spent years working with Linux, I&amp;rsquo;ve come to appreciate the importance of log files in troubleshooting and maintenance. However, with modern systems generating an overwhelming amount of log data, it&amp;rsquo;s easy to get bogged down in log noise - the unnecessary or redundant information that can make it tough to extract valuable insights. That&amp;rsquo;s where &lt;code&gt;jq&lt;/code&gt; comes in - a lightweight and flexible command-line JSON processor that can help tame log noise.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
