Amazon Q Developer operational investigations (Preview) - Amazon CloudWatch

Amazon Q Developer operational investigations (Preview)

Note

The Amazon Q Developer operational investigations feature is in preview release and is subject to change. It is currently available only in the US East (N. Virginia) Region.

The Amazon Q Developer operational investigations feature is a generative AI-powered assistant that can help you respond to incidents in your system. It uses generative AI to scan your system's telemetry and quickly surface suggestions that might be related to your issue. These suggestions include metrics, logs, deployment events, and root-cause hypotheses. For a complete list of types of data that the AI assitant can surface, see Insights that Amazon Q Developer can surface in investigations

For each suggestion, you decide whether to add it to the investigation findings or to discard it. This helps the Amazon Q Developer refine and iterate toward the root cause of the issue. Amazon Q Developer can can help you you find the root cause without having to manually identify and query multiple metrics and other sources of telemetry and events. A troubleshooting issue that would have taken hours of searching and switching between different consoles can be solved in a much shorter time.

You can create investigations in three 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 asking a question in Amazon Q chat. The question could be something 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.

After you start an investigation with any of these methods, Amazon Q Developer scans your system to find telemetry that might be relevant to the situation, and also generates hypotheses based on what it finds. Amazon Q Developer surfaces both the telemetry data and the hypotheses, and enables you to accept or discard each one.

Important

To help Amazon Q Developer operational investigations (Preview) provide the most relevant information, we might use certain content from Amazon Q, including but not limited to questions that you ask Amazon Q 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 and AWS responsible AI policy.

You can opt out of having your content collected to develop or improve the quality of Amazon Q Developer operational investigations (Preview) by creating an AI service opt-out policy for either Amazon Q or CloudWatch. For more information, see AI services opt-out policies in the AWS Organizations User Guide.

How investigations find data for suggestions

Investigations use 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, Amazon Q Developer will attempt to infer dependency relationships through co-occurring telemetry anomalies.

While Amazon Q Developer will continue to analyze telemetry data and provide suggestions without these features enabled, in order to ensure optimal quality and performance for Amazon Q Developer operational investigations, we strongly recommend that you enable the services and features listed in (Recommended) Best practices to enhance investigations.

Costs associated with Amazon Q Developer operational investigations

The Amazon Q Developer operational investigations feature is provided at no additional cost while in Preview release. During investigations, Amazon Q Developer 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 CloudWatch APIs (ListMetrics, GetDashboard, ListDashboards, and GetInsightRuleReport), X-Ray APIs (GetServiceGraph, GetTraceSummaries, and BatchGetTraces). Amazon Q Developer also uses AWS Cloud Control APIs which might incur usage of AWS services such as Amazon Kinesis Data Streams and AWS Lambda. Additionally, integration with AWS Chatbot which might incur usage of Amazon Simple Notification Service. 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 Amazon Q Developer operational investigations. For more information, see Amazon Kinesis Data Streams pricing, AWS Lambda pricing for Automation, and Amazon Simple Notification Service pricing.

Topics