Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-78393

Capture CPU Cgroup Information in FTDC metadata

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Networking & Observability
    • Fully Compatible
    • Security 2023-10-16, Security 2023-11-13, Security 2024-01-08, Security 2024-05-27, Security 2024-06-10, Security 2024-06-24, Networking & Obs 2024-09-30, Networking & Obs 2024-10-14, Networking & Obs 2024-10-28

      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

            Assignee:
            sophia.tan@mongodb.com Sophia Tan
            Reporter:
            kevin.arhelger@mongodb.com Kevin Arhelger
            Votes:
            21 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated:
              Resolved: