Examkin

Soru

Zorluk: OrtaCloudWatch Metrics and Alarms

A SysOps Administrator is troubleshooting an Amazon CloudWatch alarm configured to monitor a custom application metric named `ProcessingErrors` across a fleet of Amazon EC2 instances. The application code publishes this metric to CloudWatch with two dimensions: `InstanceId` and `Environment`. The CloudWatch alarm is configured to monitor the `ProcessingErrors` metric filtering by the `Environment` dimension only, in order to alert on the total aggregate error count. However, the alarm remains in the `INSUFFICIENT_DATA` state. Which of the following actions should the SysOps Administrator take to resolve this issue? (Select TWO.)

  1. Modify the application code to publish the metric using only the `Environment` dimension, omitting the `InstanceId` dimension.Cevap
  2. Update the CloudWatch alarm to use a Metric Math expression with the `SEARCH` function to query and aggregate the metrics across all instances for the specified environment.Cevap
  3. C
    Enable detailed monitoring for the EC2 instances in the Auto Scaling group to ensure custom metrics are aggregated at 1-minute intervals.
  4. D
    Create an Amazon EventBridge rule that triggers when the alarm enters the `INSUFFICIENT_DATA` state and configure it to run an AWS Systems Manager Automation document that aggregates the metric dimensions.
  5. E
    Increase the Auto Scaling group cooldown period to give the CloudWatch metric aggregator sufficient time to compile the multi-dimensional metric data.

Cevap

To resolve the dimension mismatch and aggregate the metric, the SysOps Administrator must either modify the application code to publish the metric with only the `Environment` dimension, or update the CloudWatch alarm to use a Metric Math expression with the `SEARCH` function to aggregate the metrics across all instances.
CloudWatch treats metrics with different dimension sets as distinct metrics. Therefore, a metric published with both an instance ID and an environment cannot be retrieved using only the environment dimension. Modifying the application code to publish the metric without the instance ID dimension, or updating the alarm to use a Metric Math expression with the search function to dynamically sum the metrics resolves this issue.

Adım Adım Çözüm

1
Identify why the alarm is in the `INSUFFICIENT_DATA` state despite the metric being published.
Each unique dimension combination in CloudWatch is treated as a separate metric. The alarm queries the metric with only the `Environment` dimension, but it is only published with both `InstanceId` and `Environment` dimensions, meaning the queried metric does not exist.
Understanding CloudWatch's behavior with respect to dimensions is necessary to troubleshoot why the alarm cannot find the data.
2
Evaluate resolution strategies that allow aggregation of custom metrics.
To aggregate, either publish the metric with the specific target dimension combination (e.g., only `Environment`), or use CloudWatch Metric Math to search and aggregate the existing multi-dimensional metrics dynamically.
These two methods provide the correct and supported ways to sum or average metric values across multiple dimensions in CloudWatch.

Anahtar Kavram

CloudWatch Custom Metric Dimensions and Aggregation
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

CloudWatch Metrics and Alarms

Bu konudan daha fazla soru