system-probe: Add pkg/process/monitor to tests

[vitkyrka]

What does this PR do?

The process monitor used by USM lives under pkg/process/monitor and has a test suite; run it as part of the system-probe tests to prevent it from breaking.

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

[agent-platform-auto-pr]

[Fast Unit Tests Report]

On pipeline 34433455 (CI Visibility). The following jobs did not run any unit tests:

Jobs:

• tests_deb-arm64-py3
• tests_deb-x64-py3
• tests_flavor_dogstatsd_deb-x64
• tests_flavor_heroku_deb-x64
• tests_flavor_iot_deb-x64
• tests_rpm-arm64-py3
• tests_rpm-x64-py3
• tests_windows-x64

If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-developer-experience

[gjulianm]

Minor nitpick, looks good :D

[pr-commenter]

Regression Detector

Regression Detector Results

Run ID: 3bfd4ae2-6663-4e82-a37e-0356011f94a9
Baseline: 20c0f40
Comparison: 44ccfe5

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

No significant changes in experiment optimization goals

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

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	tcp_syslog_to_blackhole	ingress throughput	+7.20	[-14.47, +28.87]
➖	basic_py_check	% cpu utilization	+0.85	[-1.75, +3.45]
➖	file_tree	memory utilization	+0.42	[+0.32, +0.51]
➖	idle	memory utilization	+0.41	[+0.37, +0.45]
➖	otel_to_otel_logs	ingress throughput	+0.06	[-0.32, +0.44]
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.01	[-0.01, +0.02]
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.21, +0.21]
➖	trace_agent_msgpack	ingress throughput	-0.00	[-0.00, +0.00]
➖	trace_agent_json	ingress throughput	-0.00	[-0.01, +0.01]
➖	pycheck_1000_100byte_tags	% cpu utilization	-0.12	[-5.02, +4.79]
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-1.81	[-4.67, +1.05]

Explanation

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".

[vitkyrka]

/merge

[dd-devflow]

🚂 MergeQueue

Pull request added to the queue.

There are 2 builds ahead! (estimated merge in less than 1h)

Use /merge -c to cancel this operation!