The Best re:Invent CloudWatch Launches: AI, OTEL & More

<p>This year's re:Invent brought a wave of exciting updates for Amazon CloudWatch, focusing heavily on observability, AI integration, and open standards. From native OpenSearch integration to moving X-Ray towards OpenTelemetry, here are the best launches you need to know about.</p> <div class="toc"> <h3>Table of Contents</h3> <ul> <li><a href="#opensearch-integration">OpenSearch ❤️ CloudWatch</a></li> <li><a href="#transaction-search">Transaction Search (Deeper Distributed Tracing)</a></li> <li><a href="#application-signals">Application Signals</a></li> <li><a href="#ai-investigation">AI Investigation</a></li> <li><a href="#new-metrics">New Metrics (More Coverage)</a></li> <li><a href="#faqs">Frequently Asked Questions</a></li> </ul> </div> <h2 id="opensearch-integration">OpenSearch ❤️ CloudWatch</h2> <p>One of the standout features is the native integration between OpenSearch and CloudWatch. This allows you to create dashboards for pre-defined use cases like VPC Flow Logs, CloudTrail Logs, and WAF Logs without the heavy lifting of setting up an entire ELK stack manually.</p> <p>The integration supports <strong>Direct Query</strong>, a serverless variant of OpenSearch where you pay for usage. While powerful, be mindful of the costs associated with serverless indexing and storage if you have high log volume.</p> <h2 id="transaction-search">Transaction Search (Deeper Distributed Tracing)</h2> <p>Transaction Search is a game-changer for distributed tracing. Enabling this feature transforms your AWS X-Ray traces into OpenTelemetry (OTEL) spans. This move signals AWS's commitment to supporting open standards over proprietary formats.</p> <h3 id="querying-spans">Querying Spans with SQL</h3> <p>With Transaction Search, you can now run SQL queries on your traces to gain deeper insights. For example, you can join Lambda logs with API Gateway logs to analyze performance and errors in a single view:</p> <pre><code class="language-sql">SELECT A.message as Message, A.event.path as Path, A.lambdaFunction.coldStart as IsColdStart, B.status as ApiGwStatus FROM "/aws/lambda/dev-ApiStack-RestApi" as A INNER JOIN "dev-ApiStack-RestApi-AccessLog" as B ON A.correlationIds.requestId = B.requestId </code></pre> <p>This ability to join and aggregate data across different log groups using SQL syntax makes troubleshooting complex serverless architectures significantly easier.</p> <h2 id="application-signals">Application Signals</h2> <p>Application Signals automatically instruments your application to provide a high-level overview of performance. It works with ECS, EKS, and Lambda, and requires the CloudWatch Agent or AWS Distro for OpenTelemetry.</p> <p>Key benefits include:</p> <ul> <li><strong>Automatic SLOs:</strong> Define Service Level Objectives for latency, availability, and errors.</li> <li><strong>Visual Overview:</strong> Get a topological view of your services and their health.</li> <li><strong>Standardized Metrics:</strong> consistent "Golden Signals" (Latency, Traffic, Errors, Saturation) out of the box.</li> </ul> <h2 id="ai-investigation">AI Investigation</h2> <p>Leveraging Amazon Q, CloudWatch now offers AI-powered investigations. This feature analyzes recent deployments, configuration changes, and alarm states to suggest potential root causes and fixes. It integrates with ticketing systems like Jira and Linear, providing a "feed" of investigation steps and AI-generated suggestions to speed up incident response.</p> <h2 id="new-metrics">New Metrics (More Coverage)</h2> <p>Several services received enhanced metric coverage:</p> <ul> <li><strong>Lambda Event Source Mapping (ESM):</strong> New metrics for <code>PolledEventCount</code>, <code>InvokedEventCount</code>, <code>FilteredOutEventCount</code>, and <code>FailedInvokeEventCount</code> give visibility into the "black box" of event triggers (e.g., SQS to Lambda).</li> <li><strong>ECS Enhanced Observability:</strong> New "enhanced" mode for Container Insights provides granular metrics like <code>ContainerCpuReserved</code> and <code>ContainerMemoryUtilization</code> at the container level.</li> <li><strong>Database Insights:</strong> Deeper insights for Aurora MySQL and PostgreSQL, summarizing logs and metrics in a unified dashboard.</li> </ul> <h2 id="faqs">Frequently Asked Questions</h2> <dl> <dt><strong>Is OpenSearch integration expensive?</strong></dt> <dd>It uses a serverless pricing model (Direct Query), which charges for indexing and storage. Costs can accumulate with high log volumes (e.g., terabytes/month), so it's important to estimate usage.</dd> <dt><strong>Do I need to change my code for Transaction Search?</strong></dt> <dd>No, enabling Transaction Search on X-Ray traces automatically converts them to OTEL spans for querying, but using the AWS Distro for OpenTelemetry (ADOT) is recommended for future-proofing.</dd> <dt><strong>What services support Application Signals?</strong></dt> <dd>Currently, it supports Amazon ECS, Amazon EKS, and AWS Lambda.</dd> </dl> <p><em>This part could not be verified: The exact pricing details for the OpenSearch integration example mentioned in sources may vary by region and usage patterns. Always check the official AWS pricing page.</em></p> <p>For more technical deep dives, check out our <a href="/tech/aws-consultancy">AWS Consultancy</a> and <a href="/tech/kubernetes-consultancy">Kubernetes</a> services.</p> <p><em>Kaynak / Source: <a href="https://awsfundamentals.com/blog/the-best-reinvent-cloudwatch-launches" target="_blank" rel="nofollow noopener">https://awsfundamentals.com/blog/the-best-reinvent-cloudwatch-launches</a></em></p>