Examkin

Soru

Zorluk: OrtaCloudWatch Dashboards and Container Insights

A SysOps Administrator is building an Amazon CloudWatch dashboard to monitor resource utilization of microservices running on an Amazon ECS cluster. All tasks in the cluster run on AWS Fargate. The Administrator enabled CloudWatch Container Insights for the cluster, but is unable to find container-level CPU and memory utilization metrics under the default AWS/ECS namespace in the CloudWatch console. Which of the following explains this behavior and identifies the correct location of these metrics?

  1. Container-level and task-level metrics collected by Container Insights are automatically published to the AWS/ECS/ContainerInsights namespace, whereas the default AWS/ECS namespace only provides cluster-level and service-level metrics.Cevap
  2. B
    Container-level metrics require enabling detailed monitoring on the underlying ECS container instances, which then publishes the metrics to the AWS/EC2 namespace.
  3. C
    Container Insights metrics must be extracted from the ECS performance logs by creating a CloudWatch metric filter on the /aws/ecs/containerinsights log group to map them to the AWS/ECS namespace.
  4. D
    Container-level metrics require configuring an Amazon EventBridge rule that triggers an AWS Lambda function to capture container performance events and push them to the default namespace.

Cevap

Container-level and task-level metrics collected by Container Insights are automatically published to the AWS/ECS/ContainerInsights namespace, whereas the default AWS/ECS namespace only provides cluster-level and service-level metrics.
The correct answer explains that Container Insights automatically sends detailed container-level and task-level metrics to the AWS/ECS/ContainerInsights namespace. The default AWS/ECS namespace only supports cluster-level and service-level metrics.

Adım Adım Çözüm

1
Identify the environment and target metrics.
The environment is Amazon ECS on AWS Fargate with Container Insights enabled. The goal is to locate container-level CPU and memory utilization metrics.
Understanding the launch type and metrics namespace behavior is crucial since Fargate abstracts away the underlying EC2 instances.
2
Compare default ECS metrics with Container Insights metrics.
Default ECS metrics are published to the AWS/ECS namespace but only at the cluster and service levels. Container Insights collects much more granular metrics at the container and task levels.
This allows the SysOps Administrator to locate the exact namespace where the granular metrics are published.
3
Determine the correct CloudWatch namespace.
Container Insights automatically delivers these metrics under the AWS/ECS/ContainerInsights namespace.
Knowing the correct namespace allows the Administrator to query the metrics and add them to the CloudWatch dashboard.

Anahtar Kavram

CloudWatch Container Insights Namespace
Bu soruyu puanla

Konular

CloudWatch Dashboards and Container Insights

Bu konudan daha fazla soru