-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not getting CPU metrics ecs_cpu_seconds_total #74
Comments
Seems to be missing only when running on EC2. Fargate is fine. It must be the case that the task stats API endpoint does not return per CPU usage when running on EC2, and that's what we're relying on: ecs_exporter/ecscollector/collector.go Lines 218 to 226 in 8c4f85e
If that's really the case, the exporter should either degrade to the total CPU usage metrics on EC2, or it should only use those in both EC2 and Fargate. I say that because I'm not sure what the use is of getting per-CPU numbers in general here. cAdvisor agrees: google/cadvisor@ec6da3a. |
Looks like this might have worked on EC2 in the past but stopped when cgroups v2 support was added here: aws/amazon-ecs-agent#3161.
|
I am using image URL “quay.io/prometheuscommunity/ecs-exporter:latest” , for ecs-exporter container. when I checked it exposing all the metrics or not, I saw it was not showing the CPU metrics.
got the same issue with the main and v0.2.1 images.
The text was updated successfully, but these errors were encountered: