• /
  • EnglishEspañolFrançais日本語한국어Português
  • 로그인지금 시작하기

Find and query your ECS monitoring data

After setting up OpenTelemetry monitoring for your Amazon ECS environment, you can find and query your data across New Relic's Infrastructure and query interfaces. This guide helps you locate your ECS metrics and create meaningful queries for monitoring and troubleshooting.

Where to find your ECS data

Your ECS monitoring data appears in multiple locations within New Relic, depending on the type of metrics and your ECS launch type.

Infrastructure monitoring

Navigate to one.newrelic.com > All Capabilities > Infrastructure to view your ECS infrastructure:

For ECS on EC2

  1. Hosts view: Filter by host to see your EC2 instances running ECS containers
  2. Containers view: See individual container performance within your ECS tasks

For ECS Fargate

  1. Containers view: Primary location for Fargate container metrics

Use the filter options to narrow down to specific clusters, services, or container names to quickly find the data you need.

Metrics and events

Go to one.newrelic.com > Query your data to:

  • Create custom charts and dashboards
  • Set up alerts based on specific metric thresholds

Query examples

Monitor container CPU utilization

SELECT average(container.cpu.utilization)
FROM Metric
WHERE ClusterName = 'your-cluster-name'
AND ServiceName = 'your-service-name'
TIMESERIES AUTO
FACET container.name
SELECT max(container.memory.usage.total) / 1024 / 1024 as 'Memory (MB)'
FROM Metric
WHERE ClusterName = 'your-cluster-name'
TIMESERIES AUTO
FACET ServiceName

Monitor host-level metrics (EC2 only)

SELECT average(1 - system.cpu.utilization) * 100 AS 'CPU used %',
average(system.memory.utilization) * 100 AS 'Memory used %'
FROM Metric
WHERE aws.ecs.launchtype = 'ec2'
AND aws.ecs.cluster.arn = 'your-cluster-arn'
TIMESERIES AUTO

Troubleshooting data gaps

If you don't see expected data:

  1. Verify collector status: Check container logs for the OpenTelemetry collector
  2. Confirm network connectivity: Ensure outbound HTTPS access to New Relic
  3. Check license key: Verify the license key is correctly configured in SSM Parameter Store
  4. Review task definition: Confirm the collector container is running with proper resource allocation

Next steps

Copyright © 2026 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.