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
- Redditor seeks real-world stacks for a persistent-memory personal AI that answers texts and emails — BrooksomidusGG · 2026-10-27
- Practical tip: use max effort for planning, xhigh for implementation in Claude Code — majidmanzarpour · 2026-10-27
- Chrome team explains WebMCP: agents get tools from your website, not a replacement for MCP — rseroter · 2026-10-27
- Agent-Native apps: why agents bypassing your UI can break business rules — rseroter · 2026-10-27
- 'My intelligence stack': developer splits AI coding work across Opus 5.5, Fable and Astra with human review gates — sh_reya · 2026-10-27
- Baseten webinar: evaluate open models for coding agents by benchmarking on your own merged PRs — baseten · 2026-10-27