---
title: "Comment by Mayank Bansal on \"The Behaviour Was the Bug: Observability for Systems Where Stack Traces Don't Help\" | Hashnode"
description: "I think we're starting to see two separate infrastructure layers emerge. One is observability capturing traces, prompts, retrieval context, and behaviour after"
url: "https://hashnode.com/posts/llm-observability-when-stack-traces-fail/6a58494b28416a9798790d34/comment/6a58596f349b1e2230c12dbf"
---

[Discussion](https://hashnode.com/posts/llm-observability-when-stack-traces-fail/6a58494b28416a9798790d34)

Comment [The Behaviour Was the Bug: Observability for Systems Where Stack Traces Don't Help](https://hashnode.com/posts/llm-observability-when-stack-traces-fail/6a58494b28416a9798790d34)

[Mayank Bansal](https://hashnode.com/@monk1)

[Jul 16](https://hashnode.com/posts/llm-observability-when-stack-traces-fail/6a58494b28416a9798790d34/comment/6a58596f349b1e2230c12dbf)

I think we're starting to see two separate infrastructure layers emerge. One is observability capturing traces, prompts, retrieval context, and behaviour after the fact. The other is runtime enforcement policies, completion validation, and execution checks before an action happens. Neither replaces the other, but together they make production agents much easier to trust.

[Alen Joy](https://hashnode.com/@alenj)

[Jul 21](https://hashnode.com/posts/llm-observability-when-stack-traces-fail/6a58494b28416a9798790d34/comment/6a58596f349b1e2230c12dbf#reply-6a5f7a957d89f1c40b5e111a)

Well put. I see them as complementary control planes. Observability gives you the evidence to improve the system, while runtime enforcement provides the guardrails that keep failures from propagating in production. As agentic systems become more capable, that separation between "observe" and "govern" is becoming a useful architectural pattern.
