Custom DataSource for AWS ECS Container Insights Metrics Not Polling | Community Feedback

naveen kumar · 2026-05-20T17:10:42.001170Z

Hi LogicMonitor Community,We are trying to build a custom AWS_CLOUDWATCH DataSource to collect per-service CPU and memory metrics from AWS ECS Container Insights.ObjectiveOur goal is to monitor CPUUtilized and MemoryUtilized for each ECS service in the prod-webapp cluster and display these metrics on a LogicMonitor dashboard.AWS Validation CompletedWe have verified using AWS CLI and CloudWatch that the following metrics are available and returning valid datapoints:Namespace: ECS/ContainerInsightsMetrics: CPUUtilized, MemoryUtilizedDimensions:ClusterName = prod-cluser-appServiceName = <ecs-service-name>Statistic: AverageCustom DataSource ConfigurationCollection Method: AWS_CLOUDWATCHActive Discovery Method: CLOUDWATCHNamespace: ECS/ContainerInsightsMetric Names: CPUUtilized, MemoryUtilizedDevice Dimension Name: ClusterNameInstance Dimension Name: ServiceNameMetrics Period: 900Datapoint Metric PathsECS/ContainerInsights>ClusterName:##system.aws.resourceid##>ServiceName:##wildvalue##>CPUUtilized>Average ECS/ContainerInsights>ClusterName:##system.aws.resourceid##>ServiceName:##wildvalue##>MemoryUtilized>AverageCurrent IssueThe DataSource status shows Not in Use, even though the AWS metrics are confirmed to exist and return data through the AWS CLI.The standard AWS_ECS_ClusterServices DataSource is working correctly in our environment, so AWS credentials and ECS monitoring are functioning as expected.QuestionHas anyone successfully implemented a custom DataSource for ECS Container Insights metrics using AWS_CLOUDWATCH? If so, are there any specific requirements or best practices for:AppliesTo expressionsActive Discovery configurationCloudWatch metric path formattingMulti-instance setupAny guidance or examples would be greatly appreciated.Thank you!

MoreDiscussions

Custom DataSource for AWS ECS Container Insights Metrics Not Polling | Community Feedback | LogicMonitor Community