githubEdit

Monitoring

circle-info

This page was generated from content adapted from the AWS Developer Guidearrow-up-right

CloudWatch metrics

  • Note You can disable CloudWatch metrics collection by setting ECS_DISABLE_METRICS=true in your Amazon ECS container agent configuration. For more information, see Amazon ECS container agent configurationarrow-up-right.

  • Note If you're using tasks with the EC2 launch type and have Linux container instances, the Amazon ECS container agent relies on Docker stats metrics to gather CPU and memory data for each container running on the instance. For burstable performance instances (T3, T3a, and T2 instances), the CPU utilization metric may reflect different data compared to instance-level CPU metrics.

  • Note In this example, the CPU utilization will only go above 100% when the CPU units are defined at the container level. If you define CPU units at the task level, the utilization will not go above the defined task-level limit.

CloudWatch Container Insights

Collecting application trace data

  • Important If you're also collecting application metrics using the AWS Distro for OpenTelemetry integration, ensure your task IAM role also contains the permissions necessary for that integration. For more information, see Collecting application metricsarrow-up-right.

Logging Amazon ECS API calls with AWS CloudTrail

  • Note These examples have been formatted for improved readability. In a CloudTrail log file, all entries and events are concatenated into a single line. In addition, this example has been limited to a single Amazon ECS entry. In a real CloudTrail log file, you see entries and events from multiple AWS services.

Last updated

Was this helpful?