Skip to content
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

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 25, 2024

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.

v1.17.0/v0.111.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.111.0

🆕 The binary release adds a new OTLP-only distro. Feel free to leave us feedback on this new distro on the opentelemetry-collector-releases issue tracker.

End User Changelog

🐛 Known bugs 🐛

  • The ocb binary has an identified bug caused by the fact that some of the providers have been marked stable and the default providers in the ocb binary still use the unstable version. In order to fix this explicitly add the default providers in your otel builder config, if not already configured:
providers:
  - gomod: go.opentelemetry.io/collector/confmap/provider/envprovider v1.17.0
  - gomod: go.opentelemetry.io/collector/confmap/provider/fileprovider v1.17.0
  - gomod: go.opentelemetry.io/collector/confmap/provider/httpprovider v1.17.0
  - gomod: go.opentelemetry.io/collector/confmap/provider/httpsprovider v1.17.0
  - gomod: go.opentelemetry.io/collector/confmap/provider/yamlprovider v1.17.0

This release removes the logging exporter. See #11337 to migrate to the debug exporter.

🛑 Breaking changes 🛑

  • service/telemetry: Change default metrics address to "localhost:8888" instead of ":8888" (#11251) This behavior can be disabled by disabling the feature gate telemetry.UseLocalHostAsDefaultMetricsAddress.
  • loggingexporter: Removed the deprecated logging exporter. Use the debug exporter instead. (#11037). You can read issue #11337 for migration instructions.

🚩 Deprecations 🚩

  • service/telemetry: Deprecate service::telemetry::metrics::address in favor of service::telemetry::metrics::readers. (#11205)
  • processorhelper: Deprecate BuildProcessorMetricName as it's no longer needed since introduction of mdatagen (#11302)

💡 Enhancements 💡

  • ocb: create docker images for OCB, per open-telemetry/opentelemetry-collector-releases#671 (#5712) Adds standard Docker images for OCB to Dockerhub and GitHub, see hub.docker.com/r/otel/opentelemetry-collector-builder
  • confighttp: Snappy compression to lazy read for memory efficiency (#11177)
  • httpsprovider: Mark the httpsprovider as stable. (#11191)
  • httpprovider: Mark the httpprovider as stable. (#11191)
  • yamlprovider: Mark the yamlprovider as stable. (#11192)
  • confmap: Allow using any YAML structure as a string when loading configuration including time.Time formats (#10659) Previously, fields with time.Time formats could not be used as strings in configurations

🧰 Bug fixes 🧰

  • processorhelper: Fix data race condition, concurrent writes to the err variable, causes UB (Undefined Behavior) (#11350)
  • cmd/builder: re-adds function to properly set and view version number of OpenTelemetry Collector Builder (ocb) binaries (#11208)
  • pdata: Unmarshal Span and SpanLink flags from JSON (#11267)

... (truncated)

Changelog

Sourced from go.opentelemetry.io/collector/pdata's changelog.

v1.18.0/v0.112.0

🛑 Breaking changes 🛑

  • service: Change Host to not implement GetExportersWithSignal (#11444) Use Host.GetExporters if still needed.
  • componentstatus: Remove deprecated NewInstanceIDWithPipelineIDs, AllPipelineIDsWithPipelineIDs, and WithPipelineIDs. Use NewInstanceID, AllPipelineIDs and WithPipelines instead. (#11363)
  • configgrpc: Removed deprecated ClientConfig.ToClientConnWithOptions/ServerConfig.ToServerWithOptions. (#11359, #9480) These methods were renamed to ClientConfig.ToClientConn/ServerConfig.ToServer in v0.111.0.
  • connector: Put connectortest in its own module (#11216)
  • exporter: Disables setting batch option to batch sender directly. (#10368) Removed WithRequestBatchFuncs(BatcherOption) in favor of WithBatchFuncs(Option), where | BatcherOption is a function that operates on batch sender and Option is one that operates | on BaseExporter
  • exporter: Made mergeFunc and mergeSplitFunc required method of exporter.Request (#10368) mergeFunc and mergeSplitFunc used to be part of the configuration pass to the exporter. Now it is changed | to be a method function of request.
  • componentprofiles: Move componentprofiles to pipelineprofiles (#11421)
  • processor: Put processortest in its own module (#11218)
  • receivertest: Removed deprecated NewNopFactoryForTypeWithSignal. Use NewNopFactoryForType instead. (#11362)
  • processor: Remove deprecated funcs from processor package (#11368)
  • receiver: Remove deprecated funcs from receiver package (#11367)
  • processorhelper: Remove deprecated funcs/types from processorhelper & componenttest (#11302)
  • service: Remove deprecated pipelines.ConfigWithPipelineID and Config.PipelinesWithPipelineID. Use pipelines.Config and Config.Pipelines instead. (#11361)

🚩 Deprecations 🚩

  • extension: Deprecate funcs that repeat extension in name (#11413) Factory.CreateExtension -> Factory.Create | Factory.ExtensionStability -> Factory.Stability

  • exporter: Deprecate funcs that repeate exporter in name (#11370) Factory.Create[Traces|Metrics|Logs|Profiles]Exporter -> Factory.Create[Traces|Metrics|Logs|Profiles] | Factory.[Traces|Metrics|Logs|Profiles]ExporterStability -> Factory.[Traces|Metrics|Logs|Profiles]Stability

🚀 New components 🚀

  • consumererrorprofiles: Add new module consumereerrorprofiles for consumer error profiles. (#11131)

💡 Enhancements 💡

  • configcompression: Add support for lz4 compression (#9128)
  • otlpexporter: Add profiles support to OTLP exporter (#11435)
  • otlphttpexporter: Add profiles support to OTLP HTTP exporter (#11450)

v1.17.0/v0.111.0

🛑 Breaking changes 🛑

  • service/telemetry: Change default metrics address to "localhost:8888" instead of ":8888" (#11251) This behavior can be disabled by disabling the feature gate 'telemetry.UseLocalHostAsDefaultMetricsAddress'.
  • componentprofiles: Removed deprecated DataTypeProfiles. Use SignalProfiles instead. (#11312)

... (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...
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

@dependabot dependabot bot added changelog/no-changelog dependencies PRs that bump a dependency dependencies-go PRs that bump a go dependency team/triage labels Oct 25, 2024
Copy link

cit-pr-commenter bot commented Oct 25, 2024

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 2c5e77f5-b463-4ef6-b939-1e83efc28f0a

Baseline: 87e6528
Comparison: 5187355
Diff

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

Fine details of change detection per experiment

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:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. 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.

  3. Its configuration does not mark it "erratic".

@dependabot dependabot bot force-pushed the dependabot/go_modules/go.opentelemetry.io/collector/pdata-1.18.0 branch from 6885210 to 27b1fdc Compare November 8, 2024 19:39
@github-actions github-actions bot added the short review PR is simple enough to be reviewed quickly label Nov 8, 2024
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>
@dependabot dependabot bot force-pushed the dependabot/go_modules/go.opentelemetry.io/collector/pdata-1.18.0 branch from 27b1fdc to 5187355 Compare November 8, 2024 20:02
@L3n41c L3n41c added team/opentelemetry OpenTelemetry team and removed team/triage labels Nov 12, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 15, 2024

Looks like go.opentelemetry.io/collector/pdata is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Nov 15, 2024
@dependabot dependabot bot deleted the dependabot/go_modules/go.opentelemetry.io/collector/pdata-1.18.0 branch November 15, 2024 19:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog dependencies PRs that bump a dependency dependencies-go PRs that bump a go dependency short review PR is simple enough to be reviewed quickly team/opentelemetry OpenTelemetry team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant