Скачать или смотреть How to Reference a CloudWatch Metric Created by Container Insights for ECS/Fargate

Learn how to create and reference a `CloudWatch` metric from Container Insights for your `ECS/Fargate` applications. This guide will walk you through the process step-by-step.
---
This video is based on the question https://stackoverflow.com/q/64164530/ asked by the user 'Claudiu Moise' ( https://stackoverflow.com/u/7805600/ ) and on the answer https://stackoverflow.com/a/64166600/ provided by the user 'Jonny Rimek' ( https://stackoverflow.com/u/4920854/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to reference a CloudWatch metric created by container insights for ECS/Fargate

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Reference a CloudWatch Metric Created by Container Insights for ECS/Fargate

If you're using Amazon ECS (Elastic Container Service) or Fargate and have enabled Container Insights for your cluster, you may have encountered a challenge when trying to create CloudWatch alarms based on the metrics generated. This article will guide you through how to correctly reference these metrics so that you can effectively monitor your containers.

The Problem

When attempting to create a CloudWatch alarm linked to metrics within your ECS cluster, you might run into issues due to the limitations of the AWS Cloud Development Kit (CDK). Despite having the metric in Container Insights, referencing it directly through the this.cluster.metric("CPUUtilized") approach may not work. This can be frustrating if you're expecting straightforward functionality from the tools designed for seamless integration.

The Solution

Here’s how to make this work by defining a custom CloudWatch metric object. Following the steps below will help you set up your alarm correctly.

1. Create a Custom Metric Object

Instead of using the pre-defined metrics, you can create your own metric object. Here's how you can do that for the NetworkTxBytes metric as an example:

[[See Video to Reveal this Text or Code Snippet]]

2. Key Components of the Metric

metricName: This is the specific metric name you want to track. In this example, it is set to NetworkTxBytes but can be replaced with other metrics such as CPUUtilized or MemoryUtilized based on your monitoring needs.

namespace: This should always be set to ECS/ContainerInsights for metrics related to ECS container insights. It defines the context within which the metric is stored.

dimensionsMap: This object maps key identifiers to your service and cluster names. These are essential for filtering the metrics you are interested in and ensuring you're monitoring the right resources.

3. Using the Custom Metric in a CloudWatch Alarm

Once you have defined your custom metric, you can proceed to create a CloudWatch alarm. Here’s how you can make an alarm that triggers based on the custom metric defined earlier:

[[See Video to Reveal this Text or Code Snippet]]

4. Checking for Metric Details

To fetch the correct namespace and dimensionsMap, utilize the AWS console. Navigate to the metrics section, and check the last tab labeled "source" where you can find the necessary details for your custom metric.

Conclusion

Creating custom CloudWatch metrics for your ECS/Fargate applications may seem complex at first, but with a little knowledge about namespaces and dimensions, it becomes manageable. By defining your own metric object, you can effectively monitor your containerized applications and make critical operational decisions based on the insights gained.

Feel free to refer back to this guide any time you need to create a CloudWatch metric or troubleshoot issues with ECS metrics. Happy coding!