AIX: add collector/python CGO flags and rtloader changes - #49108
Conversation
Files inventory check summaryFile checks results against ancestor f9c77438: Results for datadog-agent_7.79.0~devel.git.677.ec1b744.pipeline.107421845-1_amd64.deb:No change detected |
Static quality checks✅ Please find below the results from static quality gates 31 successful checks with minimal change (< 2 KiB)
On-wire sizes (compressed)
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 7852cc8 Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | +1.35 | [-1.67, +4.38] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | +1.35 | [-1.67, +4.38] | 1 | Logs |
| ➖ | docker_containers_memory | memory utilization | +0.71 | [+0.62, +0.79] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | +0.63 | [+0.40, +0.85] | 1 | Logs |
| ➖ | file_tree | memory utilization | +0.50 | [+0.45, +0.55] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | +0.45 | [+0.21, +0.68] | 1 | Logs bounds checks dashboard |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | +0.41 | [+0.27, +0.55] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | +0.10 | [-0.08, +0.28] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | +0.04 | [-0.07, +0.15] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | +0.02 | [-0.37, +0.42] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.12, +0.11] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.21, +0.20] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | -0.01 | [-0.22, +0.19] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.02 | [-0.46, +0.42] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | -0.02 | [-0.53, +0.49] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | -0.02 | [-0.20, +0.15] | 1 | Logs |
| ➖ | otlp_ingest_metrics | memory utilization | -0.02 | [-0.18, +0.13] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | -0.17 | [-0.23, -0.12] | 1 | Logs bounds checks dashboard |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -0.28 | [-0.45, -0.11] | 1 | Logs |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.28 | [-0.34, -0.22] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | -0.32 | [-0.36, -0.29] | 1 | Logs bounds checks dashboard |
| ➖ | ddot_logs | memory utilization | -0.35 | [-0.43, -0.28] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | -0.75 | [-0.86, -0.64] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | -2.44 | [-4.05, -0.84] | 1 | Logs bounds checks dashboard |
Bounds Checks: ✅ Passed
| perf | experiment | bounds_check_name | replicates_passed | observed_value | links |
|---|---|---|---|---|---|
| ✅ | docker_containers_cpu | simple_check_run | 10/10 | 685 ≥ 26 | |
| ✅ | docker_containers_memory | memory_usage | 10/10 | 280.20MiB ≤ 370MiB | |
| ✅ | docker_containers_memory | simple_check_run | 10/10 | 694 ≥ 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.24GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_1000ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | 0.20GiB ≤ 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 | 175.27MiB ≤ 181MiB | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | intake_connections | 10/10 | 3 = 3 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | memory_usage | 10/10 | 496.79MiB ≤ 550MiB | bounds checks dashboard |
| ✅ | quality_gate_logs | intake_connections | 10/10 | 3 ≤ 6 | bounds checks dashboard |
| ✅ | quality_gate_logs | memory_usage | 10/10 | 205.99MiB ≤ 220MiB | bounds checks dashboard |
| ✅ | quality_gate_logs | missed_bytes | 10/10 | 0B = 0B | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | 351.61 ≤ 2000 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | intake_connections | 10/10 | 3 ≤ 6 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | memory_usage | 10/10 | 405.60MiB ≤ 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:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
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.
-
Its configuration does not mark it "erratic".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check missed_bytes: 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 memory_usage: 10/10 replicas passed. Gate 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_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 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.
| stack_t new_stack{ .ss_sp = alt_stack, .ss_flags = 0, .ss_size = alt_stack_size }; | ||
| stack_t new_stack; | ||
| memset(&new_stack, 0, sizeof(new_stack)); | ||
| new_stack.ss_sp = (decltype(new_stack.ss_sp))alt_stack; | ||
| new_stack.ss_size = alt_stack_size; | ||
| new_stack.ss_flags = 0; |
There was a problem hiding this comment.
The fields are not ordered the same way on AIX and Linux, and some types also change, so this is a simple way to fix that without having to use macros
|
The root
This PR clearly adds AIX support. That line should be updated (either in this PR or as a tracked follow-up). |
|
For the AIX support this PR only adds some of the changes needed, I'd rather update that once we properly support it |
041ed3d to
43e5972
Compare
### What does this PR do? Add AIX support to `pkg/collector/python` and `rtloader`: - Split `#cgo !windows` LDFLAGS into `#cgo !aix,!windows` and `#cgo aix` variants across all Python C binding files, so that AIX does not link `libdatadog-agent-rtloader` via the generic non-Windows path - Add `pkg/collector/python/python_aix.go` to force `libpython3.13.so` into the XCOFF startup-load chain at process startup, making Python API symbols globally visible to C extension modules - Add AIX `#define DATADOG_AGENT_THREE` in `rtloader/rtloader/api.cpp` - Replace C++11 designated initializer for `stack_t` in `rtloader/rtloader/api.cpp` with explicit field assignments (AIX GCC does not support designated initializers in C++ mode) ### Motivation Follow-up to #49052. Cherry-picked from #47041. ### Describe how you validated your changes Cherry-picked from #47041, which has been tested manually on AIX. ### Additional Notes Co-authored-by: pierre.gimalac <pierre.gimalac@datadoghq.com>
### What does this PR do? Add live process monitoring support for AIX: - Add `pkg/process/procutil/process_aix.go`: implements the `Probe` interface by reading `/proc/<pid>/psinfo` directly (world-readable 448-byte binary, no elevated privileges required). The psinfo struct layout is vendored from the DataDog/gopsutil fork — there is no `DataDog/gopsutil` import. - Add `pkg/process/checks/system_info_aix.go`: `CollectSystemInfo` implementation for AIX via gopsutil v4. - Guard `fp.Stats.CtxSwitches` and `fp.CtxSwitches` nil dereferences in `process.go` and `process_rt.go` (AIX does not provide context switch data). - Exclude AIX from the generic `process_fallback.go` and the Linux-specific `system_info.go`. ### Motivation Follow-up to #49052 and #49108. Cherry-picked and adapted from #47041. ### Describe how you validated your changes Cherry-picked from #47041, which has been tested manually on AIX. ### Additional Notes The process collection logic was originally added in the `DataDog/gopsutil` fork. Since that fork is no longer used, the logic has been vendored directly into the agent. I'm working on upstreaming the logic to shirou/gopsutil but it's still WIP shirou/gopsutil#2028 Co-authored-by: pierre.gimalac <pierre.gimalac@datadoghq.com>
What does this PR do?
Add AIX support to
pkg/collector/pythonandrtloader:#cgo !windowsLDFLAGS into#cgo !aix,!windowsand#cgo aixvariants across all Python C binding files, so that AIX does not linklibdatadog-agent-rtloadervia the generic non-Windows pathpkg/collector/python/python_aix.goto forcelibpython3.13.sointo the XCOFF startup-load chain at process startup, making Python API symbols globally visible to C extension modules#define DATADOG_AGENT_THREEinrtloader/rtloader/api.cppstack_tinrtloader/rtloader/api.cppwith explicit field assignments (AIX GCC does not support designated initializers in C++ mode)Motivation
Follow-up to #49052. Cherry-picked from #47041.
Describe how you validated your changes
Cherry-picked from #47041, which has been tested manually on AIX.
Additional Notes