Bump go.opentelemetry.io/collector/config/configtelemetry from 0.104.0 to 0.112.0 #30425
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
changelog/no-changelog
dependencies
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 66f7b1b Optimization Goals: ❌ Significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ❌ | basic_py_check | % cpu utilization | +5.05 | [+1.23, +8.87] | 1 | Logs |
| ➖ | otel_to_otel_logs | ingress throughput | +1.34 | [+0.66, +2.03] | 1 | Logs |
| ➖ | file_tree | memory utilization | +1.03 | [+0.88, +1.17] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.31 | [-0.42, +1.03] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | +0.27 | [+0.02, +0.52] | 1 | Logs |
| ➖ | file_to_blackhole_300ms_latency | egress throughput | +0.15 | [-0.04, +0.33] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | +0.05 | [-0.01, +0.10] | 1 | Logs bounds checks dashboard |
| ➖ | uds_dogstatsd_to_api | ingress throughput | +0.01 | [-0.10, +0.12] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.01] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | -0.00 | [-0.43, +0.43] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | -0.01 | [-0.32, +0.29] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.03 | [-0.51, +0.46] | 1 | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -0.17 | [-0.22, -0.12] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | -0.79 | [-0.92, -0.66] | 1 | Logs bounds checks dashboard |
| ✅ | pycheck_lots_of_tags | % cpu utilization | -5.70 | [-8.98, -2.43] | 1 | Logs |
Bounds Checks: ❌ Failed
| perf | experiment | bounds_check_name | replicates_passed | links |
|---|---|---|---|---|
| ❌ | quality_gate_idle | memory_usage | 6/10 | bounds checks dashboard |
| ❌ | quality_gate_idle_all_features | memory_usage | 8/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 | lost_bytes | 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".
dependabot
bot
force-pushed
the
dependabot/go_modules/go.opentelemetry.io/collector/config/configtelemetry-0.112.0
branch
from
4431d79 to
7361e94
Compare
Bumps [go.opentelemetry.io/collector/config/configtelemetry](https://github.com/open-telemetry/opentelemetry-collector) from 0.104.0 to 0.112.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@v0.104.0...v0.112.0) --- updated-dependencies: - dependency-name: go.opentelemetry.io/collector/config/configtelemetry dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/go_modules/go.opentelemetry.io/collector/config/configtelemetry-0.112.0
branch
from
7361e94 to
179da4f
Compare
github-actions
bot
added
the
short review
|
Looks like go.opentelemetry.io/collector/config/configtelemetry is up-to-date now, so this is no longer needed. |
dependabot
bot
deleted the
dependabot/go_modules/go.opentelemetry.io/collector/config/configtelemetry-0.112.0
branch
Bumps go.opentelemetry.io/collector/config/configtelemetry from 0.104.0 to 0.112.0.
Release notes
Sourced from go.opentelemetry.io/collector/config/configtelemetry's releases.
... (truncated)
Changelog
Sourced from go.opentelemetry.io/collector/config/configtelemetry's changelog.
... (truncated)
Commits
fee2daa[chore] Prepare release v1.18.0/v0.112.0 (#11515)b30b542Update 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)2a9afd8Update 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)