Why LLM Observability Differs From APM
Ill_Deer_156 · reddit · 2026-07-13
After integrating LLM features into an existing APM, the author found the results lacking: traditional monitoring excels at catching slow requests but struggles to detect hallucinations, incorrect policy conclusions, or unwanted agent tool calls.
The post argues that LLM observability requires a different set of signals than standard APM, specifically:
- Complete prompt/response traces
- Tool call parameters and execution results
- Retrieval context in RAG scenarios
The author wants to know how others handle this: extending existing APMs or adopting dedicated LLM observability tools, and which traces are actually useful versus just noise during production incidents.
More from coding & agent
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11
- Investment Analyst Asks How to Build a Claude-Based Diligence Agent Stack — Careless_Tie2286 · 2026-09-11
- How Do You Catch Behavioral Regressions in LLM Agents Between Releases? — Beautiful_Belt_601 · 2026-09-11
- Treating agents like 50 First Dates: a 3-layer context system so every conversation doesn't start from zero — evielync · 2026-09-11
- Running the Firefox MCP on Android via Termux, ngrok, and mcp-proxy — Nervous-Strain7544 · 2026-09-11
- Run Firefox MCP on Android: Termux + ngrok tunnel tutorial — Nervous-Strain7544 · 2026-09-11