-
Notifications
You must be signed in to change notification settings - Fork 1.3k
CXP-2267 [agent] feat: add language data collection #37668
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
CXP-2267 [agent] feat: add language data collection #37668
Conversation
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 44790aa Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | quality_gate_logs | % cpu utilization | +2.59 | [-0.18, +5.35] | 1 | Logs bounds checks dashboard |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.88 | [+0.03, +1.73] | 1 | Logs |
➖ | ddot_logs | memory utilization | +0.49 | [+0.35, +0.63] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.47 | [+0.43, +0.51] | 1 | Logs |
➖ | file_tree | memory utilization | +0.41 | [+0.25, +0.57] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | +0.34 | [+0.17, +0.50] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.07 | [-0.54, +0.68] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | +0.03 | [-0.10, +0.15] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.27, +0.27] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.01 | [-0.63, +0.61] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.01 | [-0.61, +0.59] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.01 | [-0.62, +0.59] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.02 | [-0.26, +0.22] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | -0.02 | [-3.08, +3.04] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.05 | [-0.60, +0.51] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.05 | [-0.17, +0.07] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.05 | [-0.68, +0.58] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.16 | [-0.79, +0.48] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.70 | [-0.84, -0.55] | 1 | Logs bounds checks dashboard |
➖ | docker_containers_memory | memory utilization | -0.83 | [-0.89, -0.78] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -1.10 | [-1.17, -1.04] | 1 | Logs bounds checks dashboard |
➖ | tcp_syslog_to_blackhole | ingress throughput | -1.40 | [-1.47, -1.33] | 1 | Logs |
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_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 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.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
comp/core/workloadmeta/collectors/internal/process/process_collector.go
Outdated
Show resolved
Hide resolved
comp/core/workloadmeta/collectors/internal/process/process_collector.go
Outdated
Show resolved
Hide resolved
comp/core/workloadmeta/collectors/internal/process/process_collector_test.go
Outdated
Show resolved
Hide resolved
I think CODEOWNERS needs to be updated to include our team for this new collector. Our team isn't tagged in the review. |
e4c9fc0
to
225f714
Compare
comp/core/workloadmeta/collectors/internal/process/process_collector_test.go
Outdated
Show resolved
Hide resolved
comp/core/workloadmeta/collectors/internal/process/process_collector_test.go
Outdated
Show resolved
Hide resolved
comp/core/workloadmeta/collectors/internal/process/process_collector_test.go
Outdated
Show resolved
Hide resolved
comp/core/workloadmeta/collectors/internal/process/process_collector.go
Outdated
Show resolved
Hide resolved
wlmProcs := make([]*workloadmeta.Process, len(createdProcs)) | ||
isLanguageDataAvailable := len(languages) == len(createdProcs) // language data is not always available, so we have to check |
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.
nit: I think it make more sense to check that the language slice is not nil. languagedetection.DetectLanguage
always returns a slice that's the same size as procs
. But, detectLanguages
returns nil when the feature is not enabled.
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.
Yeah I was considering that, but I was worried that this function could then have a fatal error if the length of languages is not the same length as the processes due to the index access in the loop below. I understand we "own" both functions but it seems scary to have a fatal error as a possibility.
.github/CODEOWNERS
Outdated
@@ -596,6 +596,7 @@ | |||
/pkg/snmp/ @DataDog/ndm-core | |||
/pkg/tagger/ @DataDog/container-platform | |||
/pkg/windowsdriver/ @DataDog/windows-agent | |||
/comp/core/workloadmeta/collectors/internal/process @DataDog/container-experiences |
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.
Can you make @container-platform also a co-owner of this collector for visibility. I think if multiple teams are co-owners, only a review from 1 team is actually required but we'll still get tagged/notifs from the PR.
Also small nit: alphabetical ordering of the CODEOWNER. comp/core/workloadmeta/collectors/internal/process
would be last.
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.
added @DataDog/container-platform as a co-owner!
return collector{ | ||
id: id, | ||
catalog: catalog, | ||
clock: clock, | ||
processProbe: processProbe, | ||
config: config, | ||
systemProbeConfig: systemProbeConfig, |
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.
Slightly unrelated and doesn't need to be added right now but,
All of the wmeta collectors send the wmeta entity events via c.store.Notify(events)
instead of directly through a channel. It might make sense for uniformity to also store wmeta in the collector and feed the events in func (c *collector) collect
like that.
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.
Approved with small nits
9811293
to
6a6b4e3
Compare
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
languagedetector
to replicate functionality from process language collectorlanguage_detection.enabled
is trueMotivation
Describe how you validated your changes
go
). if wanted I can include them in this prPossible Drawbacks / Trade-offs
Additional Notes