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
- Shopify design lead on AI-era workflow: designers are becoming full-stack editors — KlausCodes · 2026-10-26
- Ultrametric open-sources Open Startup Repo to let AI agents run startup operations — garrytan · 2026-10-26
- MCP fault injection study: agent task scores drop 60% under realistic tool failures, scale doesn't help — dair_ai · 2026-10-26
- General agents burn ~140M tokens/month on LinkedIn outreach; scripts do it 60x cheaper — ChrisHarpon2 · 2026-10-26
- OpenAI upgrades Decisions API: 400 questions per call, native voice and image support — OpenAIDevs · 2026-10-26
- NLI alone rejects 5/6 new agent memories; a 0.45 similarity gate fixes it all — Alternative_Pin9598 · 2026-10-26