<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Logs on Linux Café</title>
    <link>https://mrtomlinux.org/tags/logs/</link>
    <description>Recent content in Logs on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 14 Sep 2026 11:47:13 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/logs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pulling the top 10 HTTP status codes from an Nginx access log with awk</title>
      <link>https://mrtomlinux.org/post/2026-09-14-pulling-the-top-10-http-status-codes-from-an-/</link>
      <pubDate>Mon, 14 Sep 2026 11:47:13 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-09-14-pulling-the-top-10-http-status-codes-from-an-/</guid>
      <description>&lt;h1 id=&#34;pull-the-top-10-http-status-codes-from-an-nginx-access-log-with-awk&#34;&gt;Pull the top 10 HTTP status codes from an Nginx access log with awk&lt;/h1&gt;&#xA;&lt;p&gt;When you’re running a small site or a homelab server, the access log is the first place you look for clues about what’s happening. A quick glance at the most frequent status codes can tell you whether a recent change broke something, if a bot is hammering your API, or if a mis‑configured rewrite is returning 404s for legitimate pages.&lt;br&gt;&#xA;Below is a practical, one‑liner‑heavy walk‑through that shows how to extract the top ten status codes from a standard Nginx log using only &lt;code&gt;awk&lt;/code&gt;. It covers common pitfalls, performance tricks, and a few security‑related notes that fit naturally into a daily‑use workflow.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
