AWS bedrock-agentcore documentation change
Summary
Revised content structure, updated throttle error counting semantics, and modified documentation links. Changed section headers from 'metrics' to 'observability data' terminology.
Security assessment
The throttle error count clarification improves operational transparency but doesn't address a security vulnerability. Terminology changes and link updates are editorial improvements without security implications. No evidence of security-related fixes or features added.
Diff
diff --git a/bedrock-agentcore/latest/devguide/observability-memory-metrics.md b/bedrock-agentcore/latest/devguide/observability-memory-metrics.md index 8155656dc..807cb52f2 100644 --- a//bedrock-agentcore/latest/devguide/observability-memory-metrics.md +++ b//bedrock-agentcore/latest/devguide/observability-memory-metrics.md @@ -7 +7 @@ Key memoryProvided span dataProvided log data -Amazon Bedrock AgentCore is in preview release and is subject to change. +# AgentCore generate memory observability data @@ -9,3 +9 @@ Amazon Bedrock AgentCore is in preview release and is subject to change. -# AgentCore provided memory metrics and spans - -For the AgentCore memory resource type, AgentCore outputs metrics to Amazon CloudWatch by default. AgentCore also outputs a default set of spans and logs, if you enable these. See [Enable observability for AgentCore memory, gateway, and built-in tool resources](./observability-configure.html#observability-configure-cloudwatch) to learn more about enabling spans and logs. +For the AgentCore memory resource type, AgentCore outputs metrics to Amazon CloudWatch by default. AgentCore also outputs a default set of spans and logs, if you enable these. See [Enabling observability for AgentCore runtime, memory, gateway, built-in tools, and identity resources](./observability-configure.html#observability-configure-cloudwatch) to learn more about enabling spans and logs. @@ -22 +20 @@ Latency -The total time elapsed between receiving the request and sending the final response token. Represents complete end-to-end processing of the request. For a create event, this represents the end to end time taken from last createEvent that met strategy criteria to the memory stored completed. +The total time elapsed between receiving the request and sending the final response token. Represents complete end-to-end processing of the request. @@ -47 +45 @@ Throttles -Number of invocations that the system throttled. Throttled requests don't count as invocations or errors. +Number of invocations that the system throttled. Throttled requests count as invocations, errors, and user errors. @@ -75 +73 @@ AgentCore provides structured logs that help you monitor and troubleshoot key Ag -AgentCore can output logs to CloudWatch Logs, Amazon S3, or Firehose stream. If you use a CloudWatch Logs destination, these logs are stored under the default log group `/aws/vendedlogs/bedrock-agentcore/memory/APPLICATION_LOGS/{memory_id}` or under a custom log group starting with `/aws/vendedlogs/`. See [Enable observability for AgentCore memory, gateway, and built-in tool resources](./observability-configure.html#observability-configure-cloudwatch) to learn more. +AgentCore can output logs to CloudWatch Logs, Amazon S3, or Firehose stream. If you use a CloudWatch Logs destination, these logs are stored under the default log group `/aws/vendedlogs/bedrock-agentcore/memory/APPLICATION_LOGS/{memory_id}` or under a custom log group starting with `/aws/vendedlogs/`. See [Enabling observability for AgentCore runtime, memory, gateway, built-in tools, and identity resources](./observability-configure.html#observability-configure-cloudwatch) to learn more. @@ -120 +118 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Provided runtime metrics +Runtime observability data