<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Log Analysis on 67AI Lab</title>
    <link>https://67ailab.com/tags/log-analysis/</link>
    <description>Recent content in Log Analysis on 67AI Lab</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 12 Nov 2026 13:30:00 +0000</lastBuildDate>
    <atom:link href="https://67ailab.com/tags/log-analysis/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Log Triage: Severity Is Solved, Fault Labels Are a Convention</title>
      <link>https://67ailab.com/posts/spark-eval-09-e2-log-triage/</link>
      <pubDate>Thu, 12 Nov 2026 13:30:00 +0000</pubDate>
      <guid>https://67ailab.com/posts/spark-eval-09-e2-log-triage/</guid>
      <description>&lt;p&gt;Operations teams spend their days reading log streams. For each line they ask&#xA;three things: is this a fault, how urgent is it, and what actually happened in&#xA;the last hour?&lt;/p&gt;&#xA;&lt;p&gt;It is high-volume, low-margin text work, and logs often can&amp;rsquo;t leave the site.&#xA;That makes it a natural fit for a local model, whose cost per line is close to&#xA;zero. Task E2 tests the three parts separately: label a log line by fault type,&#xA;rate an alert&amp;rsquo;s severity, and write an hourly summary for whoever is on call.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
