AWS AmazonCloudWatch documentation change
Summary
Updated OpenTelemetry documentation to emphasize CloudWatch's native support for OpenTelemetry metrics, logs, and traces, including PromQL querying, Logs Insights, and Transaction Search integration.
Security assessment
The changes are descriptive updates about OpenTelemetry integration and feature enhancements in CloudWatch. There is no mention of security vulnerabilities, patches, or security-specific configurations. The updates focus on observability capabilities, data correlation, and improved monitoring experiences without addressing security weaknesses or introducing security features.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/CloudWatch-OpenTelemetry-Sections.md b/AmazonCloudWatch/latest/monitoring/CloudWatch-OpenTelemetry-Sections.md index 6dedf5e51..513b7af3f 100644 --- a//AmazonCloudWatch/latest/monitoring/CloudWatch-OpenTelemetry-Sections.md +++ b//AmazonCloudWatch/latest/monitoring/CloudWatch-OpenTelemetry-Sections.md @@ -7 +7 @@ -OpenTelemetry is an open-source observability framework that provides IT teams with standardized protocols and tools for collecting and routing telemetry data. It delivers a unified format for instrumenting, generating, gathering, and exporting application telemetry data, such as metrics, logs, and traces to monitoring platforms for analysis and insights. By using OpenTelemetry, you can avoid vendor lock-in, ensuring flexibility in the observability solutions. +OpenTelemetry is an open-source observability framework that provides vendor-agnostic instrumentation for collecting metrics, logs, and traces from your applications. Amazon CloudWatch supports OpenTelemetry natively across all three signal types: metrics queryable with PromQL for flexible and scalable analytics, logs searchable with Logs Insights, and traces explorable with [Transaction Search](https://docs.aws.amazon.com//AmazonCloudWatch/latest/monitoring/CloudWatch-Transaction-Search.html). Because all three signals share a common data model with consistent attributes, you can correlate across metrics, logs, and traces to move from detection to root cause faster. OpenTelemetry metrics carry rich semantic labels and support higher granularity than traditional CloudWatch metrics, enabling precise filtering, aggregation, and analysis across your applications and infrastructure. @@ -9 +9 @@ OpenTelemetry is an open-source observability framework that provides IT teams w -You can use OpenTelemetry to directly send logs and traces to an OpenTelemetry Protocol (OTLP) endpoint, and get out-of-the box features like Logs Insights, LiveTail, and application performance monitoring experiences in [CloudWatch Application Signals](https://docs.aws.amazon.com//AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Monitoring-Intro.html). +CloudWatch supports OpenTelemetry metrics, allowing you to send custom OTel metrics directly to CloudWatch and query them using PromQL alongside AWS vended metrics from over 70 services. You can use PromQL to build dashboards, set CloudWatch Alarms, and explore metrics in Query Studio, the native PromQL console experience. OTel logs sent to CloudWatch are available in Logs Insights for interactive querying and in LiveTail for real-time streaming. @@ -11 +11 @@ You can use OpenTelemetry to directly send logs and traces to an OpenTelemetry P -Application Signals provides you with a unified, application-centric view of your applications, services, and dependencies, and helps you monitor and triage application health. You can also explore OTLP spans using the interactive search and analytics experience in CloudWatch to answer any questions related to application performance or end-user impact with [Transaction Search](https://docs.aws.amazon.com//AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html). You can also detect the impact on end users, find transactions in context of those issues using relevant attributes such as customer name or order number, correlate transactions to business events such as failed payments, and dive into interactions between application components to establish a root cause. Using CloudWatch, you can get complete application transaction coverage with correlated insights, helping you to accelerate mean time to resolution. +For application performance monitoring, CloudWatch [Application Signals](https://docs.aws.amazon.com//AmazonCloudWatch/latest/monitoring/CloudWatch-Application-Monitoring-Intro.html) provides a unified, application-centric view of your services and dependencies. Application Signals uses OTLP traces to help you monitor application health, triage issues, and identify the impact on end users. With Transaction Search, you can explore OTLP spans interactively, find transactions using attributes such as customer identifiers or order numbers, correlate transactions to business events such as failed payments, and trace interactions between application components to establish root cause.