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
- Gergely Orosz: Shipping 10x PRs With AI Agents, Sites Fill With Small Regressions — ducha_aiki · 2026-09-11
- Same Echo Maze prompt, three frontier models: all passed visually but shipped the same hidden bug — eyishazyer · 2026-09-11
- Astra storyboards plus Minimax H3 per-shot generation boost video success rates — Hailuo_AI · 2026-09-11
- Codex tip: use Sol with Astra and Luna sub-agents to save usage — pvncher · 2026-09-11
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11
- Cognition's SWE-2 uses a KKT duality argument in RL to shift the effort Pareto curve — YouJiacheng · 2026-09-11