AWS AmazonCloudWatch documentation change
Summary
Restructured documentation to add investigation reporting feature, introduced topic links for better navigation, and added a new section linking to security documentation. Removed detailed explanations of methods, hypothesis visualizations, and cost considerations in favor of separate topic pages.
Security assessment
The change introduces a link to 'Security in CloudWatch investigations' documentation, which indicates added security feature documentation. However, there is no evidence of addressing a specific security vulnerability or incident. The addition is proactive documentation of security practices rather than a response to a security issue.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/Investigations.md b/AmazonCloudWatch/latest/monitoring/Investigations.md index da3cc6c3c..25b169b8d 100644 --- a//AmazonCloudWatch/latest/monitoring/Investigations.md +++ b//AmazonCloudWatch/latest/monitoring/Investigations.md @@ -5,2 +4,0 @@ -Methods to create an investigationUnderstanding hypothesis visualizationsHow CloudWatch investigations finds data for suggestionsCosts associated with CloudWatch investigations - @@ -55,0 +54,4 @@ Before CloudWatch investigations is configured in your account investigations ru + * Investigation reporting + +When you complete an investigation, you can generate a comprehensive investigation report that automatically captures all investigation findings, timeline events, and recommended actions. + @@ -65,20 +67 @@ When you configure CloudWatch investigations , CloudWatch will use the provided -## Methods to create an investigation - -You can create investigations in the following ways: - - * From within many AWS consoles. For example, you can start an investigation when viewing a CloudWatch metric or alarm in the CloudWatch console, or from a Lambda function's **Monitor** tab on its properties page. - - * By following a prompt in chat with CloudWatch investigations. You can start by asking questions like "Why is my Lambda function slow today?" or "What's wrong with my database?" - - * By configuring a CloudWatch alarm action to automatically start an investigation when the alarm goes into ALARM state. - - - - -## Understanding hypothesis visualizations - -When CloudWatch investigations generates hypotheses that include multiple resources, the investigation view provides a visual representation of the causal relationships between those resources. This visual hypothesis view helps you quickly understand complex issues without reading lengthy text explanations. - -The hypothesis visualization displays resources as nodes connected by the pathways identified by CloudWatch investigations. For example, if a hypothesis involves Lambda function A affecting DynamoDB table B, you'll see two nodes visualizing the relationship. - -**Key features of hypothesis visualizations:** +###### Topics @@ -86 +69 @@ The hypothesis visualization displays resources as nodes connected by the pathwa - * **Resource nodes** \- Each AWS resource mentioned in the hypothesis appears as a distinct node, labeled with the resource type and identifier. + * [Methods to create an investigation](./creation-methods.html) @@ -88,19 +71 @@ The hypothesis visualization displays resources as nodes connected by the pathwa - * **Connections** \- Connections between nodes indicate the relationships that CloudWatch investigations has identified. - - * **Visual context** \- The layout helps you understand the scope and complexity of multi-resource issues at a glance. - - - - -This visual representation is particularly valuable for: - - * Understanding distributed system failures that span multiple services - - * Identifying upstream and downstream impact relationships - - * Quickly assessing the scope of an issue before diving into detailed analysis - - - - -###### Note + * [Understanding hypothesis visualizations](./Investigations-HypothesisVisualization.html) @@ -108 +73 @@ This visual representation is particularly valuable for: -Hypothesis visualizations are automatically generated when CloudWatch investigations identifies causal relationships between multiple resources. + * [How CloudWatch investigations finds data for suggestions](./data-usage-considerations.html) @@ -110 +75 @@ Hypothesis visualizations are automatically generated when CloudWatch investigat -## How CloudWatch investigations finds data for suggestions + * [Costs associated with CloudWatch investigations](./investigations-costs.html) @@ -112 +77 @@ Hypothesis visualizations are automatically generated when CloudWatch investigat -CloudWatch investigations uses a wide range of data sources to determine dependency relationships and plan analysis paths, including telemetry data configurations, service configurations, and observed relationships. These dependency relationships are found more easily if you use CloudWatch Application Signals and AWS X-Ray. When Application Signals and X-Ray aren't available, CloudWatch investigations will attempt to infer dependency relationships through co-occurring telemetry anomalies. + * [Insights that CloudWatch investigations can surface in investigations](./Investigations-SuggestionTypes.html) @@ -114 +79 @@ CloudWatch investigations uses a wide range of data sources to determine depende -While CloudWatch investigations will continue to analyze telemetry data and provide suggestions without these features enabled, we strongly recommend that you enable the services and features listed in [(Recommended) Best practices to enhance investigations](./Investigations-RecommendedServices.html) for optimal quality and performance for CloudWatch investigations. + * [AWS services where investigations are supported](./Investigations-Services.html) @@ -116 +81 @@ While CloudWatch investigations will continue to analyze telemetry data and prov -###### Important + * [Conduct an CloudWatch investigation without additional configuration](./Investigations-Ephemeral.html) @@ -118 +83 @@ While CloudWatch investigations will continue to analyze telemetry data and prov -To help CloudWatch investigations provide the most relevant information, we might use certain content from CloudWatch investigations, including but not limited to, questions that you ask CloudWatch investigations and its response, insights, user interactions, telemetry, and metadata for service improvements. Your trust and privacy, as well as the security of your content, is our highest priority. For more information, see [**AWS Service Terms**](https://aws.amazon.com/service-terms/) and [**AWS responsible AI policy**](https://aws.amazon.com/ai/responsible-ai/policy/). + * [Configure CloudWatch investigations](./Investigations-GetStarted.html) @@ -120 +85 @@ To help CloudWatch investigations provide the most relevant information, we migh -You can opt out of having your content collected to develop or improve the quality of CloudWatch investigations by creating an AI service opt-out policy for CloudWatch or AI Operations (aiops). For more information, see [AI services opt-out policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_ai-opt-out.html) in the AWS Organizations User Guide. + * [(Recommended) Best practices to enhance investigations](./Investigations-RecommendedServices.html) @@ -122 +87 @@ You can opt out of having your content collected to develop or improve the quali -## Costs associated with CloudWatch investigations + * [Investigate operational issues in your environment](./Investigations-Investigate.html) @@ -124 +89 @@ You can opt out of having your content collected to develop or improve the quali -CloudWatch investigations might incur AWS service usage including telemetry and resource queries and other API usage. While the majority of these will not be charged to your AWS bill, there are exceptions including, but not limited to: + * [Cross-account investigations](./Investigations-cross-account.html) @@ -126 +91 @@ CloudWatch investigations might incur AWS service usage including telemetry and - * CloudWatch APIs (`ListMetrics`, `GetDashboard`, `ListDashboards`, and `GetInsightRuleReport`) + * [Generate incident reports](./Investigations-Incident-Reports.html) @@ -128 +93 @@ CloudWatch investigations might incur AWS service usage including telemetry and - * X-Ray APIs (`GetServiceGraph`, `GetTraceSummaries`, and `BatchGetTraces`) + * [Integrations with other systems](./Investigations-Integrations.html) @@ -130 +95 @@ CloudWatch investigations might incur AWS service usage including telemetry and - * CloudWatch investigations also uses AWS Cloud Control APIs which might incur usage of AWS services such as Amazon Kinesis Data Streams and AWS Lambda. + * [Security in CloudWatch investigations](./Investigations-Security.html) @@ -132 +97 @@ CloudWatch investigations might incur AWS service usage including telemetry and - * Additionally, if you choose to integrate CloudWatch investigations in chat applications you might incur usage of Amazon Simple Notification Service. + * [CloudWatch investigations data retention](./Investigations-Retention.html) @@ -133,0 +99 @@ CloudWatch investigations might incur AWS service usage including telemetry and + * [Troubleshooting](./Investigations-Troubleshooting.html) @@ -137 +102,0 @@ CloudWatch investigations might incur AWS service usage including telemetry and -For usage of these services exceeding the AWS Free Tier, you will see charges on your AWS bill. These charges are expected to be minimal for normal usage of CloudWatch investigations. For more information, see [Amazon Kinesis Data Streams pricing](https://aws.amazon.com/kinesis/data-streams/pricing/), [AWS Lambda pricing for Automation](https://aws.amazon.com/lambda/pricing/), and [Amazon Simple Notification Service pricing](https://aws.amazon.com/sns/pricing/). @@ -145 +110 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Traces view +Identity @@ -147 +112 @@ Traces view -Insights that CloudWatch investigations can surface in investigations +Methods to create an investigation