-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Fargate checks fails when there are stopped containers in the task #1955
Comments
@zlangbert Thanks for the detailed report! We'll get this fixed in short order. |
@ofek I don't believe the code change resolved the issue. With
I think as it loops over the stats object integrations-core/ecs_fargate/datadog_checks/ecs_fargate/ecs_fargate.py Lines 121 to 125 in b079326
Let me know if you need any more info, thanks! |
@zlangbert This should be fixed in 6.5.x final via #2206 Can you confirm? |
@ofek Yes, all good on 6.5.1. Thanks! |
I'm running the agent as a sidecar in a Fargate task as described here. The fargate check continuously fails with the following error:
After some investigation I found that the ecs stats endpoint returns stopped containers stats as
null
. I use a volume in the task and Fargate creates a~internal~ecs-emptyvolume-source
container that is immediately stopped, causing an stats entry with the container id but no stats. The agent then fails to handle the null vaule.This applies not just to volumes but any container that is stopped. For example a container that runs a command and exits 0.
You can see an example of the
metadata
andstats
output here.Additional environment details (Operating System, Cloud provider, etc):
AWS Fargate platform version 1.1.0
Additional information you deem important (e.g. issue happens only occasionally):
This is related to support ticket 156356
The text was updated successfully, but these errors were encountered: