Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

move sysprobe config fetcher into subpackage #29617

Merged
merged 2 commits into from
Sep 27, 2024

Conversation

brycekahle
Copy link
Member

@brycekahle brycekahle commented Sep 26, 2024

What does this PR do?

Moves the system-probe config fetcher helpers into a subpackage.

Motivation

To avoid unnecessary imports in processes that have no need to directly communicate with system-probe.
See #29530 (comment) for an example of this import explosion.

Describe how to test/QA your changes

Possible Drawbacks / Trade-offs

Additional Notes

@brycekahle brycekahle added changelog/no-changelog team/ebpf-platform qa/done QA done before merge and regressions are covered by tests labels Sep 26, 2024
@brycekahle brycekahle added this to the 7.59.0 milestone Sep 26, 2024
Copy link

cit-pr-commenter bot commented Sep 26, 2024

Go Package Import Differences

Baseline: 13b26f1
Comparison: fbc2a1d

binaryosarchchange
agentlinuxamd64
+1, -0
+github.com/DataDog/datadog-agent/pkg/config/fetcher/sysprobe
agentlinuxarm64
+1, -0
+github.com/DataDog/datadog-agent/pkg/config/fetcher/sysprobe
agentwindowsamd64
+1, -0
+github.com/DataDog/datadog-agent/pkg/config/fetcher/sysprobe
agentdarwinamd64
+1, -0
+github.com/DataDog/datadog-agent/pkg/config/fetcher/sysprobe
agentdarwinarm64
+1, -0
+github.com/DataDog/datadog-agent/pkg/config/fetcher/sysprobe
iot-agentlinuxamd64
+1, -0
+github.com/DataDog/datadog-agent/pkg/config/fetcher/sysprobe
iot-agentlinuxarm64
+1, -0
+github.com/DataDog/datadog-agent/pkg/config/fetcher/sysprobe
heroku-agentlinuxamd64
+1, -0
+github.com/DataDog/datadog-agent/pkg/config/fetcher/sysprobe
dogstatsdlinuxamd64
+1, -0
+github.com/DataDog/datadog-agent/pkg/config/fetcher/sysprobe
dogstatsdlinuxarm64
+1, -0
+github.com/DataDog/datadog-agent/pkg/config/fetcher/sysprobe
process-agentlinuxamd64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client
process-agentlinuxarm64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client
process-agentwindowsamd64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client
process-agentdarwinamd64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client
process-agentdarwinarm64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client
heroku-process-agentlinuxamd64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client
security-agentlinuxamd64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client
security-agentlinuxarm64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client
system-probelinuxamd64
+1, -1
-github.com/DataDog/datadog-agent/pkg/config/fetcher
+github.com/DataDog/datadog-agent/pkg/config/fetcher/sysprobe
system-probelinuxarm64
+1, -1
-github.com/DataDog/datadog-agent/pkg/config/fetcher
+github.com/DataDog/datadog-agent/pkg/config/fetcher/sysprobe
system-probewindowsamd64
+1, -1
-github.com/DataDog/datadog-agent/pkg/config/fetcher
+github.com/DataDog/datadog-agent/pkg/config/fetcher/sysprobe
trace-agentlinuxamd64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client
trace-agentlinuxarm64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client
trace-agentwindowsamd64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client
trace-agentdarwinamd64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client
trace-agentdarwinarm64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client
heroku-trace-agentlinuxamd64
+0, -1
-github.com/DataDog/datadog-agent/cmd/system-probe/api/client

@pr-commenter
Copy link

pr-commenter bot commented Sep 27, 2024

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv create-vm --pipeline-id=45326973 --os-family=ubuntu

Note: This applies to commit fbc2a1d

@pr-commenter
Copy link

pr-commenter bot commented Sep 27, 2024

Regression Detector

Regression Detector Results

Run ID: 127da81b-6d8f-494c-a748-c6d25d33952a Metrics dashboard Target profiles

Baseline: 13b26f1
Comparison: fbc2a1d

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 trials links
basic_py_check % cpu utilization +2.51 [-0.23, +5.26] 1 Logs
file_tree memory utilization +0.01 [-0.08, +0.10] 1 Logs
otel_to_otel_logs ingress throughput +0.01 [-0.80, +0.81] 1 Logs
uds_dogstatsd_to_api ingress throughput +0.01 [-0.09, +0.10] 1 Logs
tcp_dd_logs_filter_exclude ingress throughput +0.00 [-0.01, +0.01] 1 Logs
tcp_syslog_to_blackhole ingress throughput -0.27 [-0.32, -0.21] 1 Logs
idle_all_features memory utilization -0.33 [-0.40, -0.26] 1 Logs
idle memory utilization -0.41 [-0.45, -0.37] 1 Logs
pycheck_lots_of_tags % cpu utilization -0.69 [-3.11, +1.73] 1 Logs
uds_dogstatsd_to_api_cpu % cpu utilization -1.24 [-1.97, -0.52] 1 Logs

Bounds Checks

perf experiment bounds_check_name replicates_passed
idle memory_usage 10/10

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

pkg/config/fetcher/sysprobe/from_sysprobe.go Outdated Show resolved Hide resolved
@brycekahle
Copy link
Member Author

/merge

@dd-devflow
Copy link

dd-devflow bot commented Sep 27, 2024

🚂 MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

Use /merge -c to cancel this operation!

@dd-devflow
Copy link

dd-devflow bot commented Sep 27, 2024

🚂 MergeQueue: pull request added to the queue

The median merge time in main is 24m.

Use /merge -c to cancel this operation!

@dd-mergequeue dd-mergequeue bot merged commit da20d15 into main Sep 27, 2024
218 of 228 checks passed
@dd-mergequeue dd-mergequeue bot deleted the bryce.kahle/sysprobe-config-fetcher branch September 27, 2024 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog component/system-probe qa/done QA done before merge and regressions are covered by tests team/ebpf-platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants