---
title: "Comment by Puneet Khandelwal on \"Why Raw CI Logs Are the Wrong Interface for AI Root Cause Analysis\" | Hashnode"
description: "Spot on. Dumping raw error logs into a prompt is just a lazy shortcut. We need structured error context instead."
url: "https://hashnode.com/posts/why-raw-ci-logs-are-the-wrong-interface-for-ai-root-cause-analysis/6ab501609ef7a4bf9aba205b/comment/6ab799ceed4f91d8ad790544"
---

[Discussion](https://hashnode.com/posts/why-raw-ci-logs-are-the-wrong-interface-for-ai-root-cause-analysis/6ab501609ef7a4bf9aba205b)

Comment [Why Raw CI Logs Are the Wrong Interface for AI Root Cause Analysis](https://hashnode.com/posts/why-raw-ci-logs-are-the-wrong-interface-for-ai-root-cause-analysis/6ab501609ef7a4bf9aba205b)

[Puneet Khandelwal](https://hashnode.com/@lifestyle4u)

[Sep 26](https://hashnode.com/posts/why-raw-ci-logs-are-the-wrong-interface-for-ai-root-cause-analysis/6ab501609ef7a4bf9aba205b/comment/6ab799ceed4f91d8ad790544)

Spot on. Dumping raw error logs into a prompt is just a lazy shortcut. We need structured error context instead.

[Vaibhav Garg](https://hashnode.com/@dustspeck)

[Sep 28](https://hashnode.com/posts/why-raw-ci-logs-are-the-wrong-interface-for-ai-root-cause-analysis/6ab501609ef7a4bf9aba205b/comment/6ab799ceed4f91d8ad790544#reply-6abae2fae04a85703a5b684f)

Thanks! The model shouldn't have to do all that digging just to get to the useful bits.
