AWS AmazonCloudWatch documentation change
Summary
Revised documentation of Metrics Insights alarm limits and evaluation constraints
Security assessment
The changes clarify operational limits and query processing constraints but do not address security vulnerabilities or introduce security features. These are general service quota updates.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/Create_Metrics_Insights_Alarm.md b/AmazonCloudWatch/latest/monitoring/Create_Metrics_Insights_Alarm.md index f611fa489..3442d757e 100644 --- a//AmazonCloudWatch/latest/monitoring/Create_Metrics_Insights_Alarm.md +++ b//AmazonCloudWatch/latest/monitoring/Create_Metrics_Insights_Alarm.md @@ -48 +48 @@ These clauses are essential for proper alarm evaluation. The `GROUP BY` clause s -CloudWatch Metrics Insights alarms use queries to evaluate multiple metrics and time series simultaneously. These alarms have specific limits that affect how your queries are processed and what data is available for alarm evaluation. +When working with CloudWatch Metrics Insights alarms, be aware of these functional limits: @@ -50 +50 @@ CloudWatch Metrics Insights alarms use queries to evaluate multiple metrics and -CloudWatch Metrics Insights alarms have the following limits: + * 200 alarms using this syntax per account per Region @@ -52 +52 @@ CloudWatch Metrics Insights alarms have the following limits: - * **Account limit** : 200 alarms per account per Region + * Only the latest 3 hours of data can be used for evaluating the alarm's conditions. However, you can visualize up to two weeks of data on the alarm's detail page graph @@ -54 +54 @@ CloudWatch Metrics Insights alarms have the following limits: - * **Data evaluation window** : Only the most recent 3 hours of data is used for alarm evaluation + * Alarms evaluating multiple time series will limit the rate of concurrent transitions to 100 @@ -56 +56 @@ CloudWatch Metrics Insights alarms have the following limits: - * Note: The alarm detail page can display up to 2 weeks of historical data for visualization + * Metrics Insights limits on the maximum number of time series analyzed or returned apply @@ -58 +57,0 @@ CloudWatch Metrics Insights alarms have the following limits: - * **Transition rate limiting** : Alarms monitoring multiple time series are limited to 100 concurrent state transitions @@ -60 +58,0 @@ CloudWatch Metrics Insights alarms have the following limits: - * **Query processing limits** : These limits apply at different stages of query execution: @@ -62 +59,0 @@ CloudWatch Metrics Insights alarms have the following limits: - * **Input processing** : A Metrics Insights query can process no more than 10,000 metrics. If your query matches more than 10,000 metrics (for example, across thousands of EC2 instances), the query will only process the first 10,000 metrics that it finds @@ -64,8 +61 @@ CloudWatch Metrics Insights alarms have the following limits: - * **Output results** : If your processed query would normally return more than 500 result rows, CloudWatch caps the results at 500. Since alarms require an ORDER BY clause, you'll receive the 500 highest or lowest results based on your sorting configuration - - - - -Understanding these limits helps you design effective queries. For instance, if you're monitoring a large fleet, consider using more specific filters to stay within the 10,000 metric processing limit, or use aggregation functions to reduce the number of result rows returned. - -For more information on Metrics Insights queries quotas and limits, see [Metrics Insights quotas](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch-metrics-insights-limits.html). +For more information on CloudWatch service quotas and limits, see [CloudWatch service quotas](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch_limits.html).