Topic starter
23/10/2026 12:45 am
TL;DR: Successful agent calls can still hide the wrong decision, according to Lumenova AI. Traces need to preserve prompts, context, tool use, identity, and policy checks so debugging and audit can reconstruct what happened.
Editorial analysis by NHI Mgmt Group, based on content published by Lumenova AI: “What to Instrument in an AI Agent: A Practical Guide to Traces, Spans, and Agent-Level Observability”.
Key questions
Q: Why do AI agent traces matter for governance even when every API call succeeds?
A: Successful calls do not prove correct behaviour because an agent can use the right interfaces and still make the wrong decision.
Q: What are the signs that AI agent observability is failing?
A: The main signs are missing tool metadata, disconnected traces between agent hops, unexplained retries, and an inability to reconcile a successful call with the actual state change it caused.
Q: How should security teams instrument AI agents so actions are reviewable later?
A: Security teams should capture the full decision path, not only the final result.
Practitioner guidance
- Instrument decision layers, not just system health Capture prompts, retrieval context, tool parameters, policy decisions, latency, and the identity each call ran under so a successful call still leaves a reviewable record.
- Mask sensitive fields before storage Redact credentials, personal data, and account numbers at capture time, while preserving structure and field names for later review.
- Preserve trace context across every agent handoff Pass a stable trace ID through multi-agent workflows so investigators can follow the sequence from trigger to tool use to outcome.
Bottom line: AI agent observability fails when teams equate successful execution with correct decision-making, because the system can complete every call and still reach the wrong outcome.
Glossary terms: AI Agent Observability, Trace Context, Policy Decision Record, Decision Provenance
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
23/10/2026 9:49 am
Decision provenance is now an identity problem, not only an observability problem: AI agents can execute with valid calls and still produce the wrong result, so the control question shifts from uptime to accountable action. When the system’s output depends on prompts, retrieval, policies, and tool use, identity evidence becomes part of the control record. Practitioners should treat trace completeness as a governance requirement, not a monitoring enhancement.
A few things that frame the scale:
- 67% of organisations still rely heavily on static credentials despite the risks they pose to agentic AI deployments, according to the 2026 Infrastructure Identity Survey.
- Only about one-third of approximately 500 organizations surveyed by McKinsey in 2026 report maturity level three or higher across agentic AI governance controls.
A question worth separating out:
Q: Should organisations treat AI agent logs as audit evidence or engineering data?
A: They should treat them as both, but with audit-grade discipline. The same record has to support troubleshooting, validation, cost attribution, and regulatory review, which means masking sensitive content, preserving identity context, and retaining records for the right period. If one use case is ignored, the entire evidence chain weakens.
👉 Read our full editorial: AI agent observability shifts from uptime to decision evidence
This post was modified 7 days ago by NHI Mgmt Group