AWS AmazonCloudWatch documentation change
Summary
Added documentation for OpenTelemetry metrics support, including comparison table with traditional CloudWatch metrics and integration notes throughout the document
Security assessment
This change documents new OpenTelemetry metrics functionality including ingestion protocol, query language, and alarm types. There is no evidence of security vulnerability fixes or security feature additions. The changes are purely about feature documentation and interoperability.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/cloudwatch_concepts.md b/AmazonCloudWatch/latest/monitoring/cloudwatch_concepts.md index aa9fe2e40..ed8a78ddc 100644 --- a//AmazonCloudWatch/latest/monitoring/cloudwatch_concepts.md +++ b//AmazonCloudWatch/latest/monitoring/cloudwatch_concepts.md @@ -5 +5 @@ -NamespacesMetricsDimensionsResolutionStatisticsUnitsPeriodsAggregationPercentilesAlarms +OpenTelemetry metricsNamespacesMetricsDimensionsResolutionStatisticsUnitsPeriodsAggregationPercentilesAlarms @@ -10,0 +11,2 @@ The following terminology and concepts are central to your understanding and use + * OpenTelemetry metrics + @@ -29,0 +32,20 @@ For information about the service quotas for CloudWatch metrics, alarms, API req +## OpenTelemetry metrics + +CloudWatch also supports metrics sent using the OpenTelemetry Protocol (OTLP). OpenTelemetry metrics use a different data model from traditional CloudWatch metrics. Instead of namespaces and dimensions, OpenTelemetry metrics use metric names with descriptive labels (key-value pairs) that follow OpenTelemetry semantic conventions. OpenTelemetry metrics support up to 150 labels per metric and support metric types including gauge, sum, histogram, and exponential histogram. + +OpenTelemetry metrics are queried using the Prometheus Query Language (PromQL) in CloudWatch Query Studio or through the Prometheus-compatible query API. You can set PromQL-based CloudWatch Alarms on OpenTelemetry metrics. + +The following table summarizes the key differences between OpenTelemetry metrics and traditional CloudWatch metrics. + +Concept | Traditional CloudWatch metrics | OpenTelemetry metrics +---|---|--- +Identity | Namespace, metric name, up to 30 dimensions | Metric name, up to 150 labels +Metric types | Single values, statistic sets | Gauge, sum, histogram, exponential histogram +Ingestion | PutMetricData API or AWS CLI | OpenTelemetry Protocol (OTLP) +Query language | GetMetricStatistics, Metrics Insights | Prometheus Query Language (PromQL) +Alarms | Standard CloudWatch Alarms | PromQL-based CloudWatch Alarms +Console experience | CloudWatch Metrics console | CloudWatch Query Studio +Retention | Up to 15 months with automatic rollup | 30 days (public preview) + +For more information, see [Send metrics using OpenTelemetry](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-OpenTelemetry-Sections.html). + @@ -126,0 +149,4 @@ You can't retrieve statistics for the following dimensions or if you specify no +###### Note + +OpenTelemetry metrics use labels instead of dimensions. Labels serve a similar purpose but follow OpenTelemetry semantic conventions and support up to 150 labels per metric. For more information, see OpenTelemetry metrics. + @@ -143,0 +170,4 @@ If you set an alarm on a high-resolution metric, you can specify a high-resoluti +###### Note + +OpenTelemetry metrics are ingested at the resolution they are sent, with no minimum granularity restriction. Resolution and rollup behavior for OpenTelemetry metrics differs from traditional CloudWatch metrics. + @@ -231,0 +262,2 @@ For more information, see [Using Amazon CloudWatch alarms](./CloudWatch_Alarms.h +For OpenTelemetry metrics, you can create PromQL-based CloudWatch Alarms. These alarms use PromQL queries to define alarm conditions, using the same query language available in CloudWatch Query Studio. +