--- title: Session Traces and Cost Controls Help Diagnose AI Agent... description: Session traces and cost controls are described as key techniques for diagnosing failures in production AI agents, where standard uptime monitoring cannot... canonical: https://daily.dev/posts/session-traces-and-cost-controls-help-diagnose-ai-agent-failures-cphogfesa twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Session Traces and Cost Controls Help Diagnose AI Agent Failures | daily.dev og:description: Session traces and cost controls are described as key techniques for diagnosing failures in production AI agents, where standard uptime monitoring cannot... og:url: https://daily.dev/posts/session-traces-and-cost-controls-help-diagnose-ai-agent-failures-cphogfesa og:image: https://api.daily.dev/og/posts/cphoGFEsa.png og:image:alt: Session Traces and Cost Controls Help Diagnose AI Agent Failures og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Session Traces and Cost Controls Help Diagnose AI Agent Failures **[InfoQ](https://daily.dev/sources/infoq)** · 3 min read · 0 upvotes · 0 comments ## Summary Session traces and cost controls are described as key techniques for diagnosing failures in production AI agents, where standard uptime monitoring cannot explain why an agent loops, calls invalid tools, or claims false completions. StackGen's principal engineer, drawing on production experience, recommends nested session traces (via Langfuse) capturing each LLM call, tool execution, and sub-agent delegation as spans, paired with hard iteration caps, per-tool call limits, and consecutive-call blocking as primary safeguards. Statistical anomaly detection comparing costs against rolling averages catches slower failures like model-routing errors and context expansion. For post-incident review, append-only redacted logs and bounded Prometheus metrics (avoiding high-cardinality session IDs in labels) are recommended, alongside OpenTelemetry's generative AI semantic conventions, LangSmith, and Arize Phoenix for evaluation. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do you debug an AI agent that keeps calling the wrong tool or gets stuck in a loop? Capture nested session traces with a tool like Langfuse, recording each LLM call, tool execution, and sub-agent delegation as an individual span with latency and token cost attached. Nesting child spans under parent traces preserves the full delegation chain across multi-agent workflows, letting engineers see the execution history that standard uptime monitoring cannot reveal. _daily.dev surfaces practical agent-debugging approaches for teams building production AI workflows._ ### What is the best way to prevent runaway costs from an AI agent in production? Enforce hard iteration caps and per-tool call limits before execution begins, combined with pre-execution checks that block identical consecutive tool requests. Because consecutive-call blocking only catches simple repetition, pairing it with statistical monitoring that compares each session's cost against the agent's rolling average catches slower anomalies like model-routing errors and unbounded context growth. _Track cost-control patterns for AI agents on daily.dev before a runaway workflow drains the budget._ ### Why shouldn't you put session IDs in Prometheus metric labels for AI agent monitoring? Dynamic session IDs create high-cardinality time series that can crash metric servers, since Prometheus labels are meant for bounded values like tool error rates or approval latency histograms, not per-session identifiers. Granular session context belongs strictly in traces or structured logs, since traces are for debugging while metrics are for alerting. _Engineers wiring up Prometheus for AI agents can find these cardinality pitfalls flagged on daily.dev._ ## Similar posts on daily.dev - [You can’t debug what you can’t see — Observability for AI Agents](https://daily.dev/posts/you-can-t-debug-what-you-can-t-see-observability-for-ai-agents-8yaiqpabv) · CNCF · 1 upvotes · 0 comments - [I Had Thousands of Agent Traces and Still Couldn’t Tell Which Sessions Failed](https://daily.dev/posts/i-had-thousands-of-agent-traces-and-still-couldn-t-tell-which-sessions-failed-5cga5d8xt) · Medium · 2 upvotes · 1 comments - [AI Agent Observability: Logging, Tracing, and Debugging Explained](https://daily.dev/posts/ai-agent-observability-logging-tracing-and-debugging-explained-95izimukh) · Machine Learning Mastery · 1 upvotes · 0 comments - [How do I monitor and trace AI agents running in Production](https://daily.dev/posts/how-do-i-monitor-and-trace-ai-agents-running-in-production-wulrtjnmd) · DigitalOcean Community · 0 upvotes · 0 comments - [Why Your AI Agent is a Black Box and How to fix it With OpenTelemetry](https://daily.dev/posts/why-your-ai-agent-is-a-black-box-and-how-to-fix-it-with-opentelemetry-oakutrahj) · DevOps.com · 0 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#observability](https://daily.dev/tags/observability), [#opentelemetry](https://daily.dev/tags/opentelemetry), [#prometheus](https://daily.dev/tags/prometheus) [View this post on daily.dev](https://daily.dev/posts/session-traces-and-cost-controls-help-diagnose-ai-agent-failures-cphogfesa) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Session Traces and Cost Controls Help Diagnose AI Agent Failures","url":"https://daily.dev/posts/session-traces-and-cost-controls-help-diagnose-ai-agent-failures-cphogfesa","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/session-traces-and-cost-controls-help-diagnose-ai-agent-failures-cphogfesa"},"datePublished":"2026-09-11T08:22:31.823Z","dateModified":"2026-10-15T02:22:57.809Z","description":"Session traces and cost controls are described as key techniques for diagnosing failures in production AI agents, where standard uptime monitoring cannot...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7f50328907360c3c2bd4611ef0b45973?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7f50328907360c3c2bd4611ef0b45973?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"InfoQ","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"InfoQ","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/afc3bced3e1e4b188dd9127017a60e0c","url":"https://daily.dev/sources/infoq"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/session-traces-and-cost-controls-help-diagnose-ai-agent-failures-cphogfesa","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,observability,opentelemetry,prometheus","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"InfoQ","item":"https://daily.dev/sources/infoq"},{"@type":"ListItem","position":3,"name":"Session Traces and Cost Controls Help Diagnose AI Agent Failures"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/session-traces-and-cost-controls-help-diagnose-ai-agent-failures-cphogfesa#faq","mainEntity":[{"@type":"Question","name":"How do you debug an AI agent that keeps calling the wrong tool or gets stuck in a loop?","acceptedAnswer":{"@type":"Answer","text":"Capture nested session traces with a tool like Langfuse, recording each LLM call, tool execution, and sub-agent delegation as an individual span with latency and token cost attached. Nesting child spans under parent traces preserves the full delegation chain across multi-agent workflows, letting engineers see the execution history that standard uptime monitoring cannot reveal. daily.dev surfaces practical agent-debugging approaches for teams building production AI workflows."}},{"@type":"Question","name":"What is the best way to prevent runaway costs from an AI agent in production?","acceptedAnswer":{"@type":"Answer","text":"Enforce hard iteration caps and per-tool call limits before execution begins, combined with pre-execution checks that block identical consecutive tool requests. Because consecutive-call blocking only catches simple repetition, pairing it with statistical monitoring that compares each session's cost against the agent's rolling average catches slower anomalies like model-routing errors and unbounded context growth. Track cost-control patterns for AI agents on daily.dev before a runaway workflow drains the budget."}},{"@type":"Question","name":"Why shouldn't you put session IDs in Prometheus metric labels for AI agent monitoring?","acceptedAnswer":{"@type":"Answer","text":"Dynamic session IDs create high-cardinality time series that can crash metric servers, since Prometheus labels are meant for bounded values like tool error rates or approval latency histograms, not per-session identifiers. Granular session context belongs strictly in traces or structured logs, since traces are for debugging while metrics are for alerting. Engineers wiring up Prometheus for AI agents can find these cardinality pitfalls flagged on daily.dev."}}]} ```