+ P Observe, evaluate, and improve your Amazon Bedrock Agents agents
Capture every step of Bedrock's own orchestration trace — the same reasoning-then-action sequence the agent runtime already emits when you enable it — as structured trace data.
What Prefactor records from Amazon Bedrock Agents
Amazon Bedrock Agents + Prefactor
Observe for Amazon Bedrock Agents
Prefactor observes your Amazon Bedrock Agents agents in real time — every LLM call, tool invocation, and custom span cap
Open → EvaluateEvaluate for Amazon Bedrock Agents
Prefactor evaluates your Amazon Bedrock Agents agents — score outcome quality against the captured spans, track drift by
Open → ObserveAct for Amazon Bedrock Agents
Prefactor acts on your Amazon Bedrock Agents agents at runtime — block, throttle, sandbox, or escalate a tool call or da
Open →How the Amazon Bedrock Agents integration works
- Bedrock's own agent runtime already emits an orchestration trace when enableTrace is set on InvokeAgent — Prefactor's spans map onto that same trace structure (modelInvocationInput/Output, actionGroupInvocationInput/Output) rather than re-deriving the reasoning order from raw output.
- Each action group call carries the actual JSON payload the action group returned, so a span shows exactly what tool was invoked and what came back — not just that an action group ran.
- Beyond auto-captured spans, use withSpan to record any custom step you define — an API call, a quality check, a business action.
Amazon Bedrock Agents integration FAQ
Do I need a dedicated package for Amazon Bedrock Agents?
You can instrument Amazon Bedrock Agents today with the framework-agnostic prefactor-core SDK; a dedicated package can be added on request.
What does Prefactor capture from Amazon Bedrock Agents?
Prefactor records agent action steps, knowledge-base lookups, action-group calls and LLM calls as structured, timestamped spans — so every Amazon Bedrock Agents run is captured as trace data you can reconstruct, search and export end to end.
Does Prefactor add latency or change how Amazon Bedrock Agents runs?
No. Observability capture is designed to stay off your agent's critical path, so it doesn't alter your Amazon Bedrock Agents logic or your users' responses. The only part that acts inline is the optional runtime guardrails you enable per agent — by design, so a high-risk or low-confidence action can be held for human approval before it executes.
Can I evaluate agents built with Amazon Bedrock Agents and catch regressions?
Yes. Once runs are captured, eval suites score quality and groundedness on real traffic, drift detection flags behaviour changes after deployment, and versioned eval history catches regressions before they ship — the observe → evaluate → improve loop applied to your Amazon Bedrock Agents agents.
Related guides
See it on your Amazon Bedrock Agents agents
Book a 15-minute setup and our team gets you tracing in production.