-
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
feat(opentelemetry): implement unified service tagging #26118
Conversation
We should add a test case for this in |
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv create-vm --pipeline-id=35469451 --os-family=ubuntu |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #26118 +/- ##
===========================================
+ Coverage 45.08% 50.24% +5.15%
===========================================
Files 2340 1587 -753
Lines 269884 137053 -132831
===========================================
- Hits 121683 68861 -52822
+ Misses 138579 64292 -74287
+ Partials 9622 3900 -5722
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
9db91e2
to
b8b22fe
Compare
Done 👍 |
b8b22fe
to
f741960
Compare
Regression DetectorRegression Detector ResultsRun ID: 68cd3260-dbf4-466e-be67-0957499d1433 Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
➖ | tcp_syslog_to_blackhole | ingress throughput | +6.47 | [-15.33, +28.27] |
➖ | pycheck_1000_100byte_tags | % cpu utilization | +0.79 | [-3.68, +5.26] |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.58 | [-2.35, +3.52] |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.02 | [-0.19, +0.22] |
➖ | trace_agent_msgpack | ingress throughput | +0.00 | [-0.00, +0.00] |
➖ | otel_to_otel_logs | ingress throughput | -0.01 | [-0.37, +0.34] |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.01 | [-0.05, +0.02] |
➖ | trace_agent_json | ingress throughput | -0.02 | [-0.04, +0.01] |
➖ | idle | memory utilization | -0.26 | [-0.30, -0.22] |
➖ | file_tree | memory utilization | -0.63 | [-0.73, -0.52] |
➖ | basic_py_check | % cpu utilization | -3.13 | [-5.93, -0.33] |
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:
-
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".
Signed-off-by: Wassim DHIF <[email protected]>
0875218
to
1b68351
Compare
/merge |
🚂 MergeQueue 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. Use |
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.
Just a couple of suggestions, but approving.
releasenotes/notes/opentelemetry-resource-attributes-ust-e379136c3a5c8046.yaml
Outdated
Show resolved
Hide resolved
🚂 MergeQueue Pull request added to the queue. There are 2 builds ahead! (estimated merge in less than 1h) Use |
…36c3a5c8046.yaml Co-authored-by: May Lee <[email protected]>
/merge |
🚂 MergeQueue 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. Use |
🚂 MergeQueue Pull request added to the queue. There are 6 builds ahead! (estimated merge in less than 3h) Use |
What does this PR do?
OpenTelemetry implements an equivalent to Datadog's Unified Service Tags
We want to support the OpenTelemetry SDK resource attributes the same as Unified Service Tags.
Motivation
This is needed to improve feature parity between Datadog and OpenTelemetry.
Additional notes
Note that OpenTelemetry SDK resource attributes are incompatible with pod/deployment level Unified Service Tags since they are applied at the container level.
Describe how to test/QA your changes
tagger-list
command, you should see Unified Service Tags for your container in both the Agent and Process Agent.