[ECS] [BUG]: Missing precpu_stats in Fargate 1.4.0 stats endpoints
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
`precpu_stats` values are not filled when running
**Which service(s) is this request for?**
ECS Fargate
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
When deploying an ECS Fargate task with platform 1.4.0, the `/task/stats` endpoint always return 0 values for the `precu_stats` block:
Task in 1.3.0:
```
"precpu_stats": {
"cpu_usage": {
"percpu_usage": [
7042259,
241056678,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0
],
"total_usage": 248098937,
"usage_in_kernelmode": 10000000,
"usage_in_usermode": 210000000
},
"online_cpus": 2,
"system_cpu_usage": 356320000000,
"throttling_data": {
"periods": 0,
"throttled_periods": 0,
"throttled_time": 0
}
},
```
Task in 1.4.0:
```
"precpu_stats": {
"cpu_usage": {
"total_usage": 0,
"usage_in_kernelmode": 0,
"usage_in_usermode": 0
},
"throttling_data": {
"periods": 0,
"throttled_periods": 0,
"throttled_time": 0
}
},
```
**Are you currently working around this issue?**
Requires fix on AWS side
**Additional context**
N/A
**Attachments**
N/A
Contributor guide
Research direction
The report concerns the ECS Fargate platform 1.4.0 /task/stats endpoint and compares its precpu_stats output with platform 1.3.0. No repository files, tests, or code entry points are mentioned; start by verifying the reported endpoint behavior and AWS ownership. Done would require precpu_stats values to be populated by the service, but the issue states that this needs an AWS-side fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100