Open eyalkoren opened 3 years ago
The libbeat/APM Server monitoring reports following metrics:
cgroup.cpu.id
cgroup.cpu.cfs.period.us
cgroup.cpu.cfs.quota.us
cgroup.cpu.stats.periods
cgroup.cpu.stats.throttled.periods
cgroup.cpu.stats.throttled.ns
cgroup.cpuacct.id
cgroup.cpuacct.total.ns
You can find the implementation for
cgroup.cpu
metricscgroup.cpuacct
metricsAPM Server issue for defining Elasticsearch mapping https://github.com/elastic/apm-server/issues/4433.
Hey folks -- apm-server is going to start indexing these fields with this pr: https://github.com/elastic/apm-server/pull/4956
are there any other cgroup cpu metrics that are going to be sent that aren't accounted for here?
@stuartnelson3 Thanks for picking this up!
are there any other cgroup cpu metrics that are going to be sent that aren't accounted for here?
AFAIK there is no agent reference implementation yet, so not sure anyone really looked into this. Is there a plan in the server team to implement that in the go agent?
There isn't currently an issue in the repo, maybe @simitt knows something though
@axw do you have an overview over when this is planned to be added?
@simitt no, sorry
Is your feature request related to a problem? Please describe. CPU metrics reported from containerised services are inaccurate.
Describe the solution you'd like So far we only support memory cgroup-based metrics, we need to apply the same for CPU.
Steps
Describe alternatives you've considered Not supporting those and keep inaccurate 🙂
Additional context <TBD - @elastic/apm-server if you can provide evidence from such inaccuracies observed in ESS, that would be great>