-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[CWS] move documentation generation into a regular task #37602
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
Conversation
Gitlab CI Configuration ChangesModified Jobssecurity_go_generate_check security_go_generate_check:
before_script:
- mkdir -p $GOPATH/pkg/mod/cache && tar xJf modcache.tar.xz -C $GOPATH/pkg/mod/cache
|| exit 101
- rm -f modcache.tar.xz
- mkdir -p $GOPATH/pkg/mod/cache && tar xJf modcache_tools.tar.xz -C $GOPATH/pkg/mod/cache
|| exit 101
- rm -f modcache_tools.tar.xz
- pip3 install wheel "git+https://github.com/DataDog/datadog-agent-dev.git@v$(cat
.dda/version)"
- - pip3 install -r docs/cloud-workload-security/scripts/requirements-docs.txt
- dda self dep sync -f legacy-tasks
- dda inv -- -e install-tools
image: registry.ddbuild.io/ci/datadog-agent-buildimages/linux-glibc-2-17-x64$CI_IMAGE_LINUX_GLIBC_2_17_X64_SUFFIX:$CI_IMAGE_LINUX_GLIBC_2_17_X64
needs:
- go_deps
- go_tools_deps
script:
- dda inv -- -e security-agent.go-generate-check
stage: source_test
tags:
- arch:amd64
variables:
KUBERNETES_CPU_REQUEST: 4 Changes Summary
ℹ️ Diff available in the job log. |
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 96e38c9 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | docker_containers_cpu | % cpu utilization | +1.53 | [-1.49, +4.54] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | +1.35 | [+1.29, +1.40] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.36 | [+0.32, +0.41] | 1 | Logs |
➖ | ddot_logs | memory utilization | +0.25 | [+0.11, +0.39] | 1 | Logs |
➖ | docker_containers_memory | memory utilization | +0.18 | [+0.07, +0.28] | 1 | Logs |
➖ | ddot_metrics | memory utilization | +0.12 | [+0.01, +0.24] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.10 | [-0.48, +0.67] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.07 | [-0.55, +0.69] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.03 | [-0.20, +0.26] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.02, +0.03] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.28, +0.27] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.01 | [-0.57, +0.54] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.02 | [-0.56, +0.52] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.05 | [-0.64, +0.55] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.08 | [-0.71, +0.55] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.10 | [-0.72, +0.51] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.19 | [-0.31, -0.06] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -0.21 | [-0.27, -0.16] | 1 | Logs bounds checks dashboard |
➖ | otlp_ingest_metrics | memory utilization | -0.36 | [-0.52, -0.20] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.48 | [-0.56, -0.40] | 1 | Logs bounds checks dashboard |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.64 | [-1.54, +0.26] | 1 | Logs |
➖ | file_tree | memory utilization | -1.00 | [-1.15, -0.84] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | -2.65 | [-5.38, +0.09] | 1 | Logs bounds checks dashboard |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | docker_containers_cpu | simple_check_run | 10/10 | |
✅ | docker_containers_memory | memory_usage | 10/10 | |
✅ | docker_containers_memory | simple_check_run | 10/10 | |
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | memory_usage | 10/10 | 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_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 memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 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.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
07dccd5
to
83f3c78
Compare
83f3c78
to
6e5376d
Compare
6e5376d
to
b2197ec
Compare
570c339
to
ecf8168
Compare
/merge |
View all feedbacks in Devflow UI.
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.
The expected merge time in
|
What does this PR do?
This PR brings the CWS documentation generation to regular
tasks
instead of a ad-hocscripts
folder in the docs. This will allow simpler usage, and to include it incws-go-generate
.Motivation
Describe how you validated your changes
Possible Drawbacks / Trade-offs
Additional Notes