Skip to content

gohai/cpu: collect L1/L2/L3 cache sizes and CPU packages on Darwin#48312

Open
rahulkaukuntla wants to merge 5 commits intomainfrom
auto-jira/AGENTCFG-47-gohai-darwin-cpu-cache-sizes
Open

gohai/cpu: collect L1/L2/L3 cache sizes and CPU packages on Darwin#48312
rahulkaukuntla wants to merge 5 commits intomainfrom
auto-jira/AGENTCFG-47-gohai-darwin-cpu-cache-sizes

Conversation

@rahulkaukuntla
Copy link
Contributor

@rahulkaukuntla rahulkaukuntla commented Mar 24, 2026

Summary

Addresses all Darwin gaps identified in AGENTCFG-47 (Pierre Gimalac's comments):

pkg/gohai/cpu (Darwin):

  • Collect CacheSizeL1Bytes, CacheSizeL2Bytes, CacheSizeL3Bytes via hw.l1dcachesize, hw.l2cachesize, hw.l3cachesize
  • Collect CPUPkgs via hw.packages
  • Compute CacheSizeKB as sum of available cache levels / 1024 (mirrors Linux ARM64)
  • Fall back to hw.cpufamily for Family when machdep.cpu.family returns ENOENT (Apple Silicon)

pkg/gohai/platform (Darwin):

  • Populate HardwarePlatform from uname.Machine (equivalent to uname -i on Linux)

Apple Silicon graceful degradation:

  • getSysctlOptional maps both ENOENT and EINVAL to ErrNotCollectable — needed because hw.l3cachesize returns EINVAL on Apple Silicon (key exists in MIB but hardware has no discrete L3)
  • Family falls back from machdep.cpu.family (Intel) to hw.cpufamily (all Macs)

Not addressed (noted as "not very interesting for customers" per ticket):

  • cpu.CPUNumaNodes on Darwin — macOS doesn't expose NUMA topology
  • Linux/amd64 CPU package/cache fields — requires a larger refactor to share /sys scanning logic from the ARM64 impl

Test plan

  • go test -tags test ./pkg/gohai/cpu/... ./pkg/gohai/platform/... — all pass on Apple Silicon
  • dda inv linter.go --targets=./pkg/gohai/cpu,./pkg/gohai/platform — 0 issues
  • I also verified that the new metrics appear in the gohai payload

Fixes AGENTCFG-47

🤖 Generated with Claude Code

Add `getSysctlUint64Int64` (via `hw.l1dcachesize`, `hw.l2cachesize`,
`hw.l3cachesize`) and populate `CPUPkgs` via `hw.packages` on Darwin.
`getSysctlOptional` handles both ENOENT and EINVAL so Apple Silicon
(which returns EINVAL for hw.l3cachesize) degrades gracefully to
ErrNotCollectable rather than propagating an unexpected error.

Fixes AGENTCFG-47

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@dd-octo-sts dd-octo-sts bot added the internal Identify a non-fork PR label Mar 24, 2026
@github-actions github-actions bot added the short review PR is simple enough to be reviewed quickly label Mar 24, 2026
Based on Pierre Gimalac's ticket comments:

- cpu: fall back to hw.cpufamily when machdep.cpu.family returns ENOENT
  (Apple Silicon doesn't expose machdep.cpu.family)
- cpu: compute CacheSizeKB from L1+L2+L3 bytes / 1024, mirroring
  Linux ARM64 behavior
- platform: populate HardwarePlatform from uname.Machine on Darwin
  (equivalent to `uname -i` on Linux)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions bot added medium review PR review might take time and removed short review PR is simple enough to be reviewed quickly labels Mar 24, 2026
@rahulkaukuntla
Copy link
Contributor Author

@codex review

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1cad362905

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

machine := utils.StringFromBytes(uname.Machine[:])
platformInfo.Machine = utils.NewValue(machine)
// HardwarePlatform mirrors Machine on Darwin (equivalent to uname -i)
platformInfo.HardwarePlatform = utils.NewValue(machine)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Override hardware_platform when Rosetta translation is detected

When the agent runs as an x86_64 process under Rosetta on Apple Silicon, fillPlatformInfo() intentionally rewrites Machine to arm64, but HardwarePlatform is now initialized from uname.Machine and never updated in that Rosetta branch. This leaves contradictory architecture fields (machine=arm64 but hardware_platform=x86_64) and can misreport host architecture to downstream metadata consumers that rely on hardware_platform.

Useful? React with 👍 / 👎.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch — fixed in 05ff40a. The Rosetta override block now also sets HardwarePlatform = "arm64" alongside Machine and Processor, keeping all three architecture fields consistent.

…lock

When running as an x86_64 process under Rosetta 2, fillPlatformInfo
already overrides Machine to "arm64" to reflect actual hardware.
HardwarePlatform, now populated from uname.Machine in updateUnameInfo,
was not updated in that same block, leaving Machine="arm64" but
HardwarePlatform="x86_64" — contradictory metadata downstream.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented Mar 24, 2026

Files inventory check summary

File checks results against ancestor 17ae85ff:

Results for datadog-agent_7.79.0~devel.git.108.cb149d2.pipeline.104210333-1_amd64.deb:

No change detected

@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented Mar 24, 2026

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 17ae85f
📊 Static Quality Gates Dashboard
🔗 SQG Job

30 successful checks with minimal change (< 2 KiB)
Quality gate Current Size
agent_deb_amd64 752.807 MiB
agent_deb_amd64_fips 709.763 MiB
agent_heroku_amd64 313.157 MiB
agent_rpm_amd64 752.791 MiB
agent_rpm_amd64_fips 709.746 MiB
agent_rpm_arm64 731.153 MiB
agent_rpm_arm64_fips 691.140 MiB
agent_suse_amd64 752.791 MiB
agent_suse_amd64_fips 709.746 MiB
agent_suse_arm64 731.153 MiB
agent_suse_arm64_fips 691.140 MiB
docker_agent_amd64 813.118 MiB
docker_agent_arm64 816.241 MiB
docker_agent_jmx_amd64 1004.033 MiB
docker_agent_jmx_arm64 995.936 MiB
docker_cluster_agent_amd64 205.320 MiB
docker_cluster_agent_arm64 219.677 MiB
docker_cws_instrumentation_amd64 7.142 MiB
docker_cws_instrumentation_arm64 6.689 MiB
docker_dogstatsd_amd64 39.230 MiB
docker_dogstatsd_arm64 37.445 MiB
dogstatsd_deb_amd64 29.874 MiB
dogstatsd_deb_arm64 28.026 MiB
dogstatsd_rpm_amd64 29.874 MiB
dogstatsd_suse_amd64 29.874 MiB
iot_agent_deb_amd64 43.262 MiB
iot_agent_deb_arm64 40.309 MiB
iot_agent_deb_armhf 41.052 MiB
iot_agent_rpm_amd64 43.262 MiB
iot_agent_suse_amd64 43.262 MiB
On-wire sizes (compressed)
Quality gate Change Size (prev → curr → max)
agent_deb_amd64 -31.5 KiB (0.02% reduction) 174.826 → 174.795 → 178.360
agent_deb_amd64_fips -21.57 KiB (0.01% reduction) 165.420 → 165.399 → 172.790
agent_heroku_amd64 +6.35 KiB (0.01% increase) 74.982 → 74.988 → 79.970
agent_rpm_amd64 +26.4 KiB (0.01% increase) 177.661 → 177.687 → 181.830
agent_rpm_amd64_fips -17.66 KiB (0.01% reduction) 167.720 → 167.703 → 173.370
agent_rpm_arm64 +2.06 KiB (0.00% increase) 159.604 → 159.606 → 163.060
agent_rpm_arm64_fips -12.09 KiB (0.01% reduction) 151.461 → 151.449 → 156.170
agent_suse_amd64 +26.4 KiB (0.01% increase) 177.661 → 177.687 → 181.830
agent_suse_amd64_fips -17.66 KiB (0.01% reduction) 167.720 → 167.703 → 173.370
agent_suse_arm64 +2.06 KiB (0.00% increase) 159.604 → 159.606 → 163.060
agent_suse_arm64_fips -12.09 KiB (0.01% reduction) 151.461 → 151.449 → 156.170
docker_agent_amd64 +9.33 KiB (0.00% increase) 268.255 → 268.264 → 272.480
docker_agent_arm64 neutral 255.465 MiB → 261.060
docker_agent_jmx_amd64 +5.14 KiB (0.00% increase) 336.907 → 336.912 → 341.100
docker_agent_jmx_arm64 neutral 320.101 MiB → 325.620
docker_cluster_agent_amd64 neutral 71.926 MiB → 72.920
docker_cluster_agent_arm64 neutral 67.499 MiB → 68.220
docker_cws_instrumentation_amd64 neutral 2.999 MiB → 3.330
docker_cws_instrumentation_arm64 neutral 2.729 MiB → 3.090
docker_dogstatsd_amd64 neutral 15.169 MiB → 15.820
docker_dogstatsd_arm64 neutral 14.490 MiB → 14.830
dogstatsd_deb_amd64 neutral 7.890 MiB → 8.790
dogstatsd_deb_arm64 neutral 6.775 MiB → 7.710
dogstatsd_rpm_amd64 neutral 7.901 MiB → 8.800
dogstatsd_suse_amd64 neutral 7.901 MiB → 8.800
iot_agent_deb_amd64 neutral 11.393 MiB → 12.040
iot_agent_deb_arm64 neutral 9.698 MiB → 10.450
iot_agent_deb_armhf neutral 9.933 MiB → 10.620
iot_agent_rpm_amd64 neutral 11.410 MiB → 12.060
iot_agent_suse_amd64 neutral 11.410 MiB → 12.060

@cit-pr-commenter-54b7da
Copy link

cit-pr-commenter-54b7da bot commented Mar 24, 2026

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 2512b631-cffd-4b4b-974a-73a43ee69e4a

Baseline: 17ae85f
Comparison: cb149d2
Diff

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf experiment goal Δ mean % Δ mean % CI trials links
docker_containers_cpu % cpu utilization -0.16 [-3.21, +2.89] 1 Logs

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
ddot_logs memory utilization +0.21 [+0.15, +0.26] 1 Logs
otlp_ingest_logs memory utilization +0.19 [+0.09, +0.29] 1 Logs
quality_gate_idle_all_features memory utilization +0.15 [+0.12, +0.19] 1 Logs bounds checks dashboard
ddot_metrics_sum_delta memory utilization +0.13 [-0.04, +0.31] 1 Logs
quality_gate_logs % cpu utilization +0.11 [-1.53, +1.74] 1 Logs bounds checks dashboard
ddot_metrics memory utilization +0.06 [-0.12, +0.25] 1 Logs
quality_gate_idle memory utilization +0.06 [+0.01, +0.11] 1 Logs bounds checks dashboard
ddot_metrics_sum_cumulativetodelta_exporter memory utilization +0.03 [-0.19, +0.26] 1 Logs
file_to_blackhole_500ms_latency egress throughput +0.03 [-0.36, +0.42] 1 Logs
file_to_blackhole_1000ms_latency egress throughput +0.02 [-0.41, +0.44] 1 Logs
file_to_blackhole_100ms_latency egress throughput +0.02 [-0.07, +0.10] 1 Logs
uds_dogstatsd_to_api_v3 ingress throughput +0.01 [-0.19, +0.20] 1 Logs
tcp_dd_logs_filter_exclude ingress throughput -0.00 [-0.11, +0.11] 1 Logs
uds_dogstatsd_to_api ingress throughput -0.00 [-0.20, +0.20] 1 Logs
file_tree memory utilization -0.01 [-0.07, +0.04] 1 Logs
file_to_blackhole_0ms_latency egress throughput -0.07 [-0.52, +0.39] 1 Logs
otlp_ingest_metrics memory utilization -0.07 [-0.22, +0.09] 1 Logs
tcp_syslog_to_blackhole ingress throughput -0.10 [-0.23, +0.02] 1 Logs
docker_containers_cpu % cpu utilization -0.16 [-3.21, +2.89] 1 Logs
ddot_metrics_sum_cumulative memory utilization -0.31 [-0.46, -0.17] 1 Logs
uds_dogstatsd_20mb_12k_contexts_20_senders memory utilization -0.45 [-0.51, -0.38] 1 Logs
quality_gate_metrics_logs memory utilization -0.78 [-1.02, -0.55] 1 Logs bounds checks dashboard
docker_containers_memory memory utilization -2.01 [-2.18, -1.84] 1 Logs

Bounds Checks: ✅ Passed

perf experiment bounds_check_name replicates_passed observed_value links
docker_containers_cpu simple_check_run 10/10 728 ≥ 26
docker_containers_memory memory_usage 10/10 277.18MiB ≤ 370MiB
docker_containers_memory simple_check_run 10/10 609 ≥ 26
file_to_blackhole_0ms_latency memory_usage 10/10 0.19GiB ≤ 1.20GiB
file_to_blackhole_0ms_latency missed_bytes 10/10 0B = 0B
file_to_blackhole_1000ms_latency memory_usage 10/10 0.23GiB ≤ 1.20GiB
file_to_blackhole_1000ms_latency missed_bytes 10/10 0B = 0B
file_to_blackhole_100ms_latency memory_usage 10/10 0.19GiB ≤ 1.20GiB
file_to_blackhole_100ms_latency missed_bytes 10/10 0B = 0B
file_to_blackhole_500ms_latency memory_usage 10/10 0.21GiB ≤ 1.20GiB
file_to_blackhole_500ms_latency missed_bytes 10/10 0B = 0B
quality_gate_idle intake_connections 10/10 3 = 3 bounds checks dashboard
quality_gate_idle memory_usage 10/10 174.45MiB ≤ 175MiB bounds checks dashboard
quality_gate_idle_all_features intake_connections 10/10 2 ≤ 3 bounds checks dashboard
quality_gate_idle_all_features memory_usage 10/10 509.98MiB ≤ 550MiB bounds checks dashboard
quality_gate_logs intake_connections 10/10 4 ≤ 6 bounds checks dashboard
quality_gate_logs memory_usage 10/10 205.18MiB ≤ 220MiB bounds checks dashboard
quality_gate_logs missed_bytes 10/10 0B = 0B bounds checks dashboard
quality_gate_metrics_logs cpu_usage 10/10 330.83 ≤ 2000 bounds checks dashboard
quality_gate_metrics_logs intake_connections 10/10 4 ≤ 6 bounds checks dashboard
quality_gate_metrics_logs memory_usage 10/10 399.00MiB ≤ 475MiB bounds checks dashboard
quality_gate_metrics_logs missed_bytes 10/10 0B = 0B bounds checks dashboard

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

  • ✅ = significantly better comparison variant performance
  • ❌ = significantly worse comparison variant performance
  • ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

  3. Its configuration does not mark it "erratic".

CI Pass/Fail Decision

Passed. All Quality Gates passed.

  • quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
  • quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.

@rahulkaukuntla rahulkaukuntla added the qa/done QA done before merge and regressions are covered by tests label Mar 24, 2026
@rahulkaukuntla rahulkaukuntla marked this pull request as ready for review March 24, 2026 19:12
@rahulkaukuntla rahulkaukuntla requested a review from a team as a code owner March 24, 2026 19:13
@rahulkaukuntla rahulkaukuntla requested a review from dustmop March 24, 2026 19:13
Copy link
Contributor

@dustmop dustmop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, with one small nitpick


// type returned by sysctl is uint64, stored as uint64; treats EINVAL as ErrNotCollectable
// because some keys (e.g. hw.l3cachesize) return EINVAL on hardware that lacks the feature
func getSysctlUint64Int64(key string) utils.Value[uint64] {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm curious why you're naming this function with both Uint64 and Int64? Why not just call it getSysctlInt64?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point — renamed to getSysctlInt64. The storage type is already conveyed by the return type Value[uint64], so the Uint64 prefix was redundant.

rahulkaukuntla and others added 2 commits March 24, 2026 16:11
The storage type is already conveyed by the return type Value[uint64].

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Identify a non-fork PR medium review PR review might take time qa/done QA done before merge and regressions are covered by tests team/agent-configuration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants