You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2021/03/31 02:23:05 UTC
[GitHub] [skywalking] hanahmily commented on pull request #6479: Support k8s monitoring
hanahmily commented on pull request #6479:
URL: https://github.com/apache/skywalking/pull/6479#issuecomment-810708089
> > **Why node status is a bar graph?**
> > Status is a label value，use bar graph can see how many nodes in there, and if status was changed we could see different colors. If issue #6569 finished, we could have another choice to show status more directly.
> > 
>
> > **And could you fill the missing units? Such as CPU usage, should 100 or 1 be expected as 100%?**
> > In k8s, the CPU usually used cores as the units, such as `1 core, 200m core(about 0.2core )`, I think we can discuss it.
> > @hanahmily @wu-sheng
For CPU request and limit metrics, the unit should be `m` which represents an absolute quantity, never as a relative quantity; 0.1 is the same amount of CPU on a single-core, dual-core, or 48-core machine. And I prefer to use `m` due to avoiding floating-point numbers. Any number which is finer than 1m, for example, 0.1m, will be rounded up to 1m under the hood.
If we want a percentage of the requested CPU, `cpu_cores_requests/cpu_cores`could get the desired result.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org