AWS ECS/ECR monitoring integration

Access to this feature depends on your subscription level. Requires Infrastructure Pro.

New Relic Infrastructure's integrations include an integration for reporting your Amazon EC2 Container Service (ECS) data and your Amazon EC2 Container Registry (ECR) data to New Relic products. This document explains the integration's features, how to activate it, and what data can be reported.

Features

With New Relic's ECS/ECR monitoring integration, you can monitor reserved vs. utilized capacity, task execution, and registry of containers. AWS integration data is also available for analysis and chart creation in Insights.

Activate integration

To enable this integration:

  1. Make sure you have installed the Infrastructure agent before you activate AWS integrations from your Infrastructure account.
  2. Follow standard procedures to Connect AWS services to Infrastructure.

Configuration and polling

You can change the polling frequency and filter data using configuration options.

Default polling information for the AWS ECS/ECR integration:

  • New Relic polling interval: 5 minutes
  • Amazon CloudWatch data interval: 1 minute or 5 minutes

Find and use data

To find this integration's data in Infrastructure, go to infrastructure.newrelic.com > Integrations > Amazon Web Services and select one of the AWS ECS/ECR integration links.

In New Relic Insights, data is attached to the ComputeSample event type, with a provider value of EcsCluster.

The integration collects these ECR/ECS definitions:

Name Description
ClusterName This dimension filters the data you request for all resources in a specified cluster. All Amazon ECS metrics are filtered by ClusterName.
ServiceName This dimension filters the data you request for all resources in a specified service within a specified cluster.

For more on how to find and use integration data, see Understand integration data.

Metric data

The ECS/ECR integration collects the following data:

For full descriptions of these metrics, see Amazon's documentation on ECS and ECR.

Cluster and service metrics

Name Data type
CPUUtilization percent
MemoryUtilization percent

Cluster metrics

Name Data type
CPUReservation percent
MemoryReservation percent

Service metrics

Name Description
Active Service The number of services that are running on the cluster in an ACTIVE state
Pending Tasks Number of tasks in the cluster that are in PENDING state
Running Tasks Number of tasks in the cluster that are in RUNNING state
Registered Instances Number of container instances registered into the cluster

Inventory data

Inventory data provides information about the service's state and configuration. For more about inventory data, see Understand and use data.

aws/ecs/cluster​

Attribute name Description
status The status of the cluster. The valid values are ACTIVE or INACTIVE. ACTIVE indicates that you can register container instances with the cluster and the associated instances can accept tasks.
name User-generated string to identify the cluster.
awsRegion AWS region where the cluster is running.

aws/ecs/service

Attribute name Description
status The status of the service. The valid values are ACTIVE, DRAINING or INACTIVE. ACTIVE means the instance accepts new tasks, DRAINING means the instance prevents new tasks from being started and notifies the service scheduler to move tasks to other instances in the cluster, generally used with the purpose of maintaining the instance or scale it down and INACTIVE means the instance is not active.
clusterName User-generated string to identify the cluster.
serviceName User-generated string to identify the service.
launchType Type of infrastructure on which tasks and services are hosted. The valid values are EC2 and FARGATE.
awsRegion AWS region where the service is running.
deploymentMaximumPercent Upper limit on the number of service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount.
deploymentMinimumPercent Lower limit on the number of service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount.
desiredCount

The number of instantiations of the specified task definition to place and keep running on the cluster.
taskDefinition ARN of the task definition file that describes the containers that form the application.

For more help

Recommendations for learning more: