Amazon Bedrock AgentCore is in preview release and is subject to change.
View observability data for your Amazon Bedrock AgentCore agents
After implementing observability in your agent, you can view the collected metrics and traces in both the CloudWatch console generative AI observability page and in CloudWatch Logs. Refer to the following sections to learn how to view metrics for your agents.
View data using generative AI observability in Amazon CloudWatch
The CloudWatch generative AI observability page displays all of the service-provided metrics output by the AgentCore agent runtime,
as well as span- and trace-derived data if you have enabled instrumentation in your agent code. To view the observability dashboard in CloudWatch, open the
Amazon CloudWatch GenAi Observability
With generative AI observability in CloudWatch, you can view tailored dashboards with graphs and other visualizations of your data, as well as error breakdowns, trace visualizations and more. To learn more about using generative AI observability in CloudWatch, including how to look at your agents' individual session and trace data, see Amazon Bedrock AgentCore agents in the Amazon CloudWatch user guide.
View other data in CloudWatch
All of the service-provided metrics and spans can also be viewed in CloudWatch, along with any metrics that your instrumented agent code outputs.
To view this data, refer to the following sections.
Logs
-
Open the CloudWatch
console. -
In the left hand navigation pane, expand Logs and select Log groups
-
Use the search field to find the log group for your agent, memory, or gateway resource.
AgentCore agent log groups have the following format:
-
Standard logs - stdout/stderr output
-
Location: /aws/bedrock-agentcore/runtimes/<agent_id>-<endpoint_name>/[runtime-logs] <UUID>
-
Contains: Runtime errors, application logs, debugging statements
-
Example Usage:
-
print("Processing request...") # Appears in standard logs
-
logging.info("Request processed successfully") # Appears in standard logs
-
-
-
OTEL structured logs - Detailed operation information
-
Location: /aws/bedrock-agentcore/runtimes/<agent_id>-<endpoint_name>/runtime-logs
-
Contains: Execution details, error tracking, performance data
-
Automatic collection: No additional code required - generated by ADOT instrumentation
-
Benefits: Can include correlation IDs linking logs to relevant traces
-
-
Traces and Spans
Traces provide visibility into request execution paths through your agent:
-
Location:
/aws/spans/default
-
Access via: CloudWatch Transaction Search console
-
Requirements: CloudWatch Transaction Search must be enabled
Traces automatically capture:
-
Agent invocation sequences
-
Integration with framework components (LangChain, etc.)
-
LLM calls and responses
-
Tool invocations and results
-
Error paths and exceptions
For distributed tracing across services, you can use standard HTTP headers:
-
AWS X-Ray format:
X-Amzn-Trace-Id: Root=1-5759e988-bd862e3fe1be46a994272793;Parent=53995c3f42cd8ad8;Sampled=1
-
W3C format:
traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01
To view traces:
-
Navigate to CloudWatch console
-
Select Transaction Search from the left navigation
-
Filter by service name or other criteria
-
Select a trace to view the detailed execution graph
Metrics
If you have enabled observability by instrumenting your agent code as described in Enabling AgentCore runtime observability, your agent automatically generates OTEL metrics, which are sent to CloudWatch using Enhanced Metric Format (EMF):
-
Namespace:
bedrock-agentcore
-
Access via: CloudWatch Metrics console
-
Contents: Custom metrics generated by your agent code and frameworks
-
Automatic collection: No additional code required - generated by ADOT instrumentation
In addition to agent-emitted metrics, the AgentCore service publishes standard service metrics to CloudWatch. Refer to AgentCore provided runtime metrics for a list of these metrics.