{"version":"2.1.265","anchor":"cgroup-cpu-accounting-rewritten-to-read-cpuacctusage-direct","canonical_anchor":"cgroup-cpu-accounting-rewritten-to-read-cpuacctusage-direct","heading":"cgroup CPU accounting rewritten to read cpuacct.usage directly, adds shell CPU tracking","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/cgroup-cpu-accounting-rewritten-to-read-cpuacctusage-direct","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### cgroup CPU accounting rewritten to read cpuacct.usage directly, adds shell CPU tracking\n\nCPU telemetry now reads cgroup usage from a fixed path and adds a new shell CPU time metric\n\n**What**\n\nThe telemetry that reports CPU usage broken down by session phase (`tengu_tool_cpu_by_phase`) now reads CPU accounting data from a fixed cgroup path, `\/sys\/fs\/cgroup\/cpuacct`, plus a per-tool cgroup's `cpuacct.usage` file. It also adds a new `*_shell_cpu_ms` metric, reported alongside the existing `*_wall_ms`, `*_cli_cpu_ms`, and `*_tools_cpu_ms` metrics when shell cgroup data is available.\n\n**Why**\n\nThis gives more precise, directly-read CPU accounting and adds visibility specifically into CPU time spent in shell subprocesses, on top of the existing CLI-versus-tools breakdown.\n\n- Area: Telemetry\n- Names: `cpuacct.usage`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}