AWS AmazonCloudWatch documentation change
Summary
Updated agent metrics terminology, added authentication-related metrics documentation, removed detailed sessions/traces analysis section, updated images and headings
Security assessment
Added documentation for 'Inbound Auth' and 'Outbound Auth' metrics improves visibility into authentication mechanisms but doesn't address a specific vulnerability. Removed content about error monitoring appears to be general documentation restructuring rather than security-related changes.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/agent-view.md b/AmazonCloudWatch/latest/monitoring/agent-view.md index 5c9f0136a..252b1d23e 100644 --- a//AmazonCloudWatch/latest/monitoring/agent-view.md +++ b//AmazonCloudWatch/latest/monitoring/agent-view.md @@ -15 +15 @@ The following Agent metrics are supported: - * Agents/Aliases – Number of agents and aliases instrumented and emitting spans + * Agents/Endpoints – Number of agents and aliases instrumented and emitting spans @@ -65 +65 @@ You can view the details of the Agent by expanding the agent name. - + @@ -82,0 +83,4 @@ The _Agent metrics_ dashboard include metrics which are derived from sampled spa + * Inbound Auth:Authorization and access token calls – Number of incoming authentication requests processed by the agent, including authorization checks and access token validations from external clients or services + + * Outbound Auth:Usage distribution – Distribution pattern of outbound authentication methods used by the agent, showing the frequency and types of authentication mechanisms employed when accessing external services + @@ -97,58 +100,0 @@ The _Runtime metrics_ dashboard includes metrics that AgentCore Runtime automati -**Agent details - Sessions** - -An Agent can have several Sessions. View session in the _Sessions_ tab. Use the **Filter sessions** or sort the columns to find the required session. - -Choose the **Session ID** to view the session summary metrics and the list of traces belonging to that session. Session metrics include: - - * Traces – Number of traces belonging to the sessions - - * Server errors – Count of system errors during request processing. High levels of server-side errors can indicate potential infrastructure or service issues that require investigation - - * Client errors – Client errors are errors resulting from invalid requests. High levels of client-side errors can indicate issues with request formatting or permissions - - * Throttles – Number of requests throttled relevant to this session due to exceeding allowed TPS (Transactions Per Second) - - * Sessions details – Meta data about the session such as start time, end time, and session ID - - - - -To analyze a list of Traces in a session, choose **Filter traces** to narrow down or sort the table columns to bubble up the particular Trace you want to investigate. - -After you select a Trace, the right-pane displays the details of the Trace. For each Trace, you can see the Trace summary, Spans, and Trace content details. - -Under **Trace summary** , you can view the following metrics: - -###### Note - -Summary page fields are consistent across **Agent view** , **Sessions view** , and **Traces view**. - - * Spans – Number of spans within a Trace - - * Server errors – Count of system errors during request processing. High levels of server-side errors can indicate potential infrastructure or service issues that require investigation - - * Client errors – Client errors are errors resulting from invalid requests. High levels of client-side errors can indicate issues with request formatting or permissions - - * Throttles – Number of requests throttle relevant to this session due to exceeding allowed TPS (Transactions Per Second) - - * P95 span latency – The 95-percentile latency of across all invocation of this particular span. Note that a span can be used across many agents - - * Trace details – Meta data about the trace such as start time, end time, and Trace ID - - - - - - -Choose **Timeline** to view the duration of each span and to understand the span that took the longest and contributed to a slow response. - - - -To analyze span relationships and subsequent calls choose **Trajectory** to understand the interconnected relationship of the spans and subsequent calls from these spans. - -Under **Spans** , select an individual span event to review the span data in its original form. Review the span data in its original form. For granular troubleshooting, select the **Events** tab to examine model inputs and outputs. - -**Agent details - Traces** - -Each agent might have multiple traces. View trace details in the **Traces** tab. Choose **Filter traces** or sort the columns to find the required Trace. - @@ -161 +107 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Amazon Bedrock AgentCore Agents +Agents @@ -163 +109 @@ Amazon Bedrock AgentCore Agents -Session view +Agent details - Sessions