← Latest papers
🤖 AI

Detect, Localize, and Explain: Interactive Hierarchical Log Anomaly Analytics with LLM Augmentation

This paper presents Krone-viz, an interactive visualization system that leverages a novel hierarchical log abstraction and modular orchestration framework to enable precise anomaly detection, localization, and explanation through selective LLM augmentation and human-in-the-loop refinement.

Original authors: Lei Ma, Suhani Chaudhary, Ethan Shanbaum, Athanasios Tassiadamis, Peter M. VanNostrand, Dennis M. Hofmann, Haowen Xu, Elke Rundensteiner

Published 2026-05-12
📖 5 min read🧠 Deep dive

Original authors: Lei Ma, Suhani Chaudhary, Ethan Shanbaum, Athanasios Tassiadamis, Peter M. VanNostrand, Dennis M. Hofmann, Haowen Xu, Elke Rundensteiner

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a detective trying to solve a crime, but instead of a few witness statements, you are handed a 10,000-page transcript of a chaotic, non-stop radio broadcast. Every sentence is a tiny fragment of a conversation, but they are all jumbled together in a single, flat list. This is what computer "logs" usually look like: endless streams of text that tell a system what it's doing, but in a way that is incredibly hard for humans to understand.

The paper introduces Krone (and its visual tool, Krone-viz), a new way to make sense of this chaos. Here is how it works, explained through simple analogies:

1. The Problem: The "Flat" List vs. The "Story"

Most current tools treat logs like a flat list of ingredients. If a cake burns, they just say, "The cake is bad." They don't tell you which ingredient was wrong, when it went bad, or why.

  • The Old Way: Looking at a flat list of 10,000 log entries and trying to find the one typo that caused a crash. It's like trying to find a specific sentence in a novel where every word is written on a single line.
  • The Krone Way: Krone realizes that computers don't just do random things; they follow a story structure. Every action has a Who (Entity), a What (Action), and a Result (Status).

2. The Solution: Building a "Family Tree" for Logs

Krone takes that messy, flat list and organizes it into a hierarchical family tree (called a Krone-Tree).

  • The Analogy: Imagine taking a messy pile of Lego bricks and sorting them into boxes: "Wheels," "Windows," and "Doors." Then, you group those boxes into "Car Parts," and those into "The Whole Car."
  • How it works: Krone uses an AI (a Large Language Model, or LLM) to read the logs and say, "Ah, this log entry is about a 'Session' (Who) that 'Opened' (What) and 'Started' (Result)." It builds a map where every log entry knows exactly where it fits in the bigger picture.

3. The Detective Work: "Divide and Conquer"

Once the logs are organized into this tree, Krone doesn't check every single brick. It uses a smart, step-by-step strategy to find the problem.

  • The "Lightweight" Filter: First, Krone uses a simple, fast rule-checker (like a spell-checker) to scan the logs. If a log entry looks normal, it ignores it. This is like a security guard quickly waving through people with clear IDs.
  • The "AI" Detective: If the simple checker finds something weird, then it calls in the expensive, super-smart AI detective (the LLM) to investigate.
  • The "Bottom-Up" Strategy: Krone starts by checking the smallest details (the "Status" level, like "Started" or "Failed"). If it finds a problem there, it stops immediately. It doesn't waste time checking the bigger "Action" or "Entity" levels because the problem is already found. This saves a massive amount of money and computing power.

4. The "Cheat Sheet": Learning as You Go

One of Krone's coolest features is that it remembers what it has learned.

  • The Analogy: Imagine a detective who keeps a notebook. If they solve a mystery about a "broken door hinge" today, they write it down. Next time they see a "broken door hinge," they don't need to call the expensive AI detective again; they just look at their notebook.
  • How it works: Krone builds a Knowledge Base. If it analyzes a specific type of log sequence and finds it's normal (or abnormal), it saves that result. If that same sequence appears again later, Krone reuses the answer. This makes the system faster and cheaper over time.

5. The Visual Tool: Krone-viz

The paper presents Krone-viz, a dashboard that lets human engineers see all of this happening in real-time.

  • What you can do:
    1. See the Tree: You can watch the flat logs turn into the organized family tree.
    2. Spot the Glitch: You can see exactly which "branch" of the tree is broken.
    3. Read the Explanation: The AI writes a plain-English explanation of why it thinks something is wrong.
    4. Fix the AI: If the AI makes a mistake, you can correct it. The system learns from your correction and updates its "notebook" so it doesn't make the same mistake again.

Summary

In short, Krone stops treating computer logs like a chaotic wall of text. Instead, it organizes them into a structured story, uses a smart "check first, ask later" strategy to find errors, and remembers its findings to get smarter and cheaper over time. Krone-viz is the window that lets humans watch this process, understand the AI's reasoning, and fix it if needed.

Note: The paper specifically tested this system on a standard dataset called HDFS (a type of file storage system log) to prove it works better and costs less than previous methods. It does not claim to be used for medical diagnosis or other specific industries yet.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →