Bump to opentelemetry-mapping-go v0.11.0 #21740
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4615d0a to
a4b5d9e
Compare
a4b5d9e to
71df56a
Compare
Go Package Import DifferencesBaseline: a65179f
|
mackjmr
approved these changes
Dec 22, 2023
Bloop Bleep... Dogbot HereRegression Detector ResultsRun ID: 01d90553-2db8-482c-9bcb-4179fbea9c2e 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 |
|---|---|---|---|---|
| ➖ | file_to_blackhole | % cpu utilization | +0.97 | [-5.59, +7.52] |
| ➖ | idle | memory utilization | -0.66 | [-0.70, -0.62] |
| ➖ | file_tree | memory utilization | -1.56 | [-1.70, -1.42] |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI |
|---|---|---|---|---|
| ➖ | file_to_blackhole | % cpu utilization | +0.97 | [-5.59, +7.52] |
| ➖ | process_agent_standard_check_with_stats | memory utilization | +0.79 | [+0.73, +0.86] |
| ➖ | process_agent_real_time_mode | memory utilization | +0.41 | [+0.37, +0.45] |
| ➖ | trace_agent_json | ingress throughput | +0.02 | [-0.01, +0.04] |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.06, +0.06] |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.04, +0.04] |
| ➖ | trace_agent_msgpack | ingress throughput | -0.03 | [-0.05, -0.01] |
| ➖ | process_agent_standard_check | memory utilization | -0.16 | [-0.22, -0.11] |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -0.58 | [-0.65, -0.52] |
| ➖ | idle | memory utilization | -0.66 | [-0.70, -0.62] |
| ➖ | otel_to_otel_logs | ingress throughput | -1.42 | [-2.14, -0.71] |
| ➖ | file_tree | memory utilization | -1.56 | [-1.70, -1.42] |
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".
vickenty
approved these changes
Jan 4, 2024
Co-authored-by: Mackenzie <63265430+mackjmr@users.noreply.github.com>
hush-hush
approved these changes
Jan 5, 2024
ahmed-mez
approved these changes
Jan 5, 2024
chouquette
reviewed
Jan 5, 2024
|
/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. you can cancel this operation by commenting your pull request with |
chouquette
approved these changes
Jan 5, 2024
|
🚂 MergeQueue Added to the queue. There are 3 builds ahead of this PR! (estimated merge in less than 1h) you can cancel this operation by commenting your pull request with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
logs.Translatorfor logs implementationMotivation
On the Datadog exporter, we want to report a metric related to missing hostnames in resources. For now, this will be a Datadog exporter only thing, so here the telemetry settings are set to noop, either explicitly (as in the trace agent) or implicitly (as in the metrics and logs where we disable telemetry).
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
This is an internal change only, with no user-facing impact.
Reviewer's Checklist
Triagemilestone is set.major_changelabel if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.changelog/no-changeloglabel has been applied.qa/skip-qalabel, with required eitherqa/doneorqa/no-code-changelabels, are applied.team/..label has been applied, indicating the team(s) that should QA this change.need-change/operatorandneed-change/helmlabels have been applied.k8s/<min-version>label, indicating the lowest Kubernetes version compatible with this feature.