-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
ecs_task_cpu_utilization
and ecs_task_cpu_usage_vcpu
have the wrong units listed
#35640
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
receiver/awsecscontainermetrics
Is your feature request related to a problem? Please describe.
I believe that the README.md regarding the
awsecscontainermetrics
receiver might be a little misleading. In the table it's specified that the unit for the metricecs_task_cpu_utilized
is a percentage, but I believe it should be units of vCPU. On a similar note the metricecs_task_cpu_usage_vcpu
is the one that should be a percentage.Describe the solution you'd like
I'd like to receive some clarification on the mentioned metrics and/or a fix in the README.md
Describe alternatives you've considered
No response
Additional context
This first caught my attention when I tried to create an alert based on the
ecs_task_cpu_utilized
metric (e.g.ecs_task_cpu_utilized > 80
for when the CPU usage exceeded 80 percent). However this metric went up to values such as 200+. I then looked more into whatecs_task_cpu_usage_vcpu
gives as a value. It seemed that values such as 0.2 are pretty low in terms of vCPU. I then made a comparison and came to the conclusion thatecs_task_cpu_usage_vcpu * 1024 = ecs_task_cpu_utilized
. I've since reconfigured my alert to be something likeecs_task_cpu_utilized / ecs_task_cpu_reserved * 100
to actually get a percentage of CPU usage.The text was updated successfully, but these errors were encountered: