[SERVER-78393] Capture CPU Cgroup Information in FTDC metadata Created: 23/Jun/23  Updated: 22/Jan/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Kevin Arhelger Assignee: Brad Moore
Resolution: Unresolved Votes: 5
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Server Security
Sprint: Security 2023-10-16, Security 2023-11-13, Security 2024-01-08, Security 2024-02-19
Participants:

 Description   

Currently we expose memory cgroup information in FTDC.

It would be beneficial to capture the effective CPU cgroup information in FTDC as well.

This would relay if a MongoDB service contained a systemd CPUQuota or are running a Kubernetes pod with a requests.cpu limit.

My thought was a calculated, fractional value under hostInfo.system that represents the effective number of cores this process could be scheduled on.

https://docs.kernel.org/scheduler/sched-bwc.html
https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html


Generated at Thu Feb 08 06:38:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.