-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Update ProgramData Directory permissions #32117
Update ProgramData Directory permissions #32117
Conversation
[Fast Unit Tests Report] On pipeline 52281716 (CI Visibility). The following jobs did not run any unit tests: Jobs:
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-devx-help |
Package size comparisonComparison with ancestor Diff per package
Decision |
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv aws.create-vm --pipeline-id=52281716 --os-family=ubuntu Note: This applies to commit 8cd00f3 |
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 274cdd8 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | quality_gate_logs | % cpu utilization | +2.75 | [-0.54, +6.05] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | +1.58 | [+1.52, +1.65] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +1.47 | [+0.77, +2.17] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | +0.64 | [+0.56, +0.72] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.20 | [-0.27, +0.67] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.04 | [-0.73, +0.82] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.04 | [-0.85, +0.93] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.03 | [-0.61, +0.68] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.02 | [-0.82, +0.86] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.01 | [-0.82, +0.84] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.00 | [-0.76, +0.77] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.13, +0.10] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -0.06 | [-0.10, -0.03] | 1 | Logs bounds checks dashboard |
➖ | file_tree | memory utilization | -0.40 | [-0.53, -0.27] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.47 | [-1.27, +0.33] | 1 | Logs |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | 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 | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | |
✅ | quality_gate_logs | memory_usage | 10/10 |
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_all_features, 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_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
e2221aa
to
efd698a
Compare
Uncompressed package size comparisonComparison with ancestor Diff per package
Decision |
tools/windows/DatadogAgentInstaller/CustomActions/ConfigureUserCustomActions.cs
Outdated
Show resolved
Hide resolved
tools/windows/DatadogAgentInstaller/CustomActions/ConfigureUserCustomActions.cs
Show resolved
Hide resolved
tools/windows/DatadogAgentInstaller/CustomActions/ConfigureUserCustomActions.cs
Show resolved
Hide resolved
tools/windows/DatadogAgentInstaller/CustomActions/ConfigureUserCustomActions.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor suggestions but otherwise looks good.
releasenotes/notes/update-programdata-permissions-6271744e48907d71.yaml
Outdated
Show resolved
Hide resolved
releasenotes/notes/update-programdata-permissions-6271744e48907d71.yaml
Outdated
Show resolved
Hide resolved
releasenotes/notes/update-programdata-permissions-6271744e48907d71.yaml
Outdated
Show resolved
Hide resolved
/merge |
Devflow running:
|
What does this PR do?
Updates permissions of ProgramData folder for windows operating systems.
Motivation
https://datadoghq.atlassian.net/browse/WINA-1232
Describe how you validated your changes
Tested by existing e2e tests.
Possible Drawbacks / Trade-offs
Removes inherited write permissions to data directory meaning any custom log, run, etc. paths the agent needs to be given explicit write access if not created by the agent.
Additional Notes