-
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
Bump go.opentelemetry.io/collector/pdata from 1.11.0 to 1.18.0 #30501
Bump go.opentelemetry.io/collector/pdata from 1.11.0 to 1.18.0 #30501
Conversation
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 87e6528 Optimization Goals: ❌ Significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
❌ | pycheck_lots_of_tags | % cpu utilization | +7.88 | [+4.38, +11.38] | 1 | Logs |
➖ | basic_py_check | % cpu utilization | +1.28 | [-2.53, +5.10] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.05 | [-0.13, +0.24] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.04 | [-0.20, +0.29] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.02 | [-0.31, +0.34] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.02 | [-0.04, +0.08] | 1 | Logs bounds checks dashboard |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.02 | [-0.11, +0.07] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.03 | [-0.48, +0.41] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.09 | [-0.57, +0.39] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.10 | [-0.15, -0.05] | 1 | Logs |
➖ | otel_to_otel_logs | ingress throughput | -0.13 | [-0.79, +0.52] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.69 | [-1.40, +0.03] | 1 | Logs |
➖ | file_tree | memory utilization | -1.31 | [-1.44, -1.19] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -3.30 | [-3.41, -3.19] | 1 | Logs bounds checks dashboard |
Bounds Checks: ❌ Failed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
❌ | quality_gate_idle | memory_usage | 4/10 | bounds checks dashboard |
❌ | file_to_blackhole_100ms_latency | lost_bytes | 7/10 | |
❌ | quality_gate_idle_all_features | memory_usage | 9/10 | bounds checks dashboard |
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | 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".
6885210
to
27b1fdc
Compare
Bumps [go.opentelemetry.io/collector/pdata](https://github.com/open-telemetry/opentelemetry-collector) from 1.11.0 to 1.18.0. - [Release notes](https://github.com/open-telemetry/opentelemetry-collector/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CHANGELOG-API.md) - [Commits](open-telemetry/opentelemetry-collector@pdata/v1.11.0...pdata/v1.18.0) --- updated-dependencies: - dependency-name: go.opentelemetry.io/collector/pdata dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
27b1fdc
to
5187355
Compare
Looks like go.opentelemetry.io/collector/pdata is up-to-date now, so this is no longer needed. |
Bumps go.opentelemetry.io/collector/pdata from 1.11.0 to 1.18.0.
Release notes
Sourced from go.opentelemetry.io/collector/pdata's releases.
... (truncated)
Changelog
Sourced from go.opentelemetry.io/collector/pdata's changelog.
... (truncated)
Commits
fee2daa
[chore] Prepare release v1.18.0/v0.112.0 (#11515)b30b542
Update github/codeql-action action to v3.27.0 (#11514)dd573f3
[chore] [exporterhelper] Update batch methods comments (#11513)6e12a02
[chore] Promote Damien Mathieu to triager role (#11508)2b6da0d
[chore] Handle nested exportertest dependency references (#11512)02ceda1
[chore] Use psuedo-version number for exportertest (#11511)2a9afd8
Update actions/cache action to v4.1.2 (#11510)11767fe
[chore] Update leaf module versions to commits with pseudo version dependenci...403c782
[chore] Remove unnecessary context from Batch.split (#11504)8f20a07
[chore] Small nits in batch processor, use generics to avoid type conversions...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)