datadog-agent icon indicating copy to clipboard operation
datadog-agent copied to clipboard

Bump go.opentelemetry.io/collector/featuregate from 1.11.0 to 1.15.0

Open dependabot[bot] opened this issue 1 year ago • 1 comments

Bumps go.opentelemetry.io/collector/featuregate from 1.11.0 to 1.15.0.

Release notes

Sourced from go.opentelemetry.io/collector/featuregate's releases.

v1.15.0/v0.109.0

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

End User Changelog

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.15.0
  - gomod: go.opentelemetry.io/collector/confmap/provider/fileprovider v1.15.0
  - gomod: go.opentelemetry.io/collector/confmap/provider/httpprovider v0.109.0
  - gomod: go.opentelemetry.io/collector/confmap/provider/httpsprovider v0.109.0
  - gomod: go.opentelemetry.io/collector/confmap/provider/yamlprovider v0.109.0

🛑 Breaking changes 🛑

  • scraperhelper: Remove deprecated ObsReport, ObsReportSettings, NewObsReport types/funcs (#11086)
  • confmap: Remove stable confmap.strictlyTypedInput gate (#11008)
  • confmap: Removes stable confmap.unifyEnvVarExpansion feature gate. (#11007)
  • ballastextension: Removes the deprecated ballastextension (#10671)
  • service: Removes stable service.disableOpenCensusBridge feature gate (#11009)

🚩 Deprecations 🚩

  • processorhelper: These funcs are not used anywhere, marking them deprecated. (#11083)

🚀 New components 🚀

  • extension/experimental/storage: Move extension/experimental/storage into a separate module (#11022)

💡 Enhancements 💡

  • configtelemetry: Add guidelines for each level of component telemetry (#10286)

  • service: move useOtelWithSDKConfigurationForInternalTelemetry gate to beta (#11091)

  • service: implement a no-op tracer provider that doesn't propagate the context (#11026) The no-op tracer provider supported by the SDK incurs a memory cost of propagating the context no matter what. This is not needed if tracing is not enabled in the Collector. This implementation of the no-op tracer provider removes the need to allocate memory when tracing is disabled.

  • envprovider: Mark module as stable (#10982)

  • fileprovider: Mark module as stable (#10983)

  • processor: Add incoming and outgoing counts for processors using processorhelper. (#10910) Any processor using the processorhelper package (this is most processors) will automatically report incoming and outgoing item counts. The new metrics are:

    • otelcol_processor_incoming_spans
    • otelcol_processor_outgoing_spans
    • otelcol_processor_incoming_metric_points
    • otelcol_processor_outgoing_metric_points

... (truncated)

Changelog

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

v1.15.0/v0.109.0

🛑 Breaking changes 🛑

  • Remove extensiontest StatusWatcher helpers: They were unused. They may be added back on a different module or after componentstatus is marked 1.0 (#11044)
  • pprofile: Change Profile ID field from a byte array to a custom data type (#11048)
  • connector: Remove deprecated connector builder (#11019)
  • exporter: Remove deprecated exporter builder (#11019)
  • extension: Remove deprecated extension builder (#11019)
  • processor: Remove deprecated processor builder (#11019)
  • receiver: Remove deprecated receiver builder (#11019)

🚩 Deprecations 🚩

  • configtelemetry: Deprecating TelemetrySettings.MeterProvider in favour of TelemetrySettings.LeveledMeterProvider (#10912)
  • extension: Deprecate extension.ConfigWatcher, extension.PipelineWatcher and extension.Dependent in favor of equivalents in the extensioncapabilities module. (#11000)
  • scraperhelper: deprecate NewScraper, should use NewScraperWithComponentType (#11082)

🚀 New components 🚀

  • extensioncapabilities: Create a new module for optional extension capabilities. (#11000)

💡 Enhancements 💡

  • connectorprofiles: Add ProfilesRouterAndConsumer interface, and NewProfilesRouter method. (#11023)
  • pprofileotlp: Introduce grpc service implementation of pprofileotlp (#11048)
  • pprofile: Introduce marshalling and unmarshalling of pprofile data (#11048)
  • service: Support profiles in the service package (#11024)

v1.14.1/v0.108.1

v1.14.0/v0.108.0

🛑 Breaking changes 🛑

  • extensions: Remove StatusWatcher interface. Use componentstatus.Watcher instead. (#10777)
  • component: Removed Status related types and functions. Use componentstatus instead. (#10777)
  • component: Remove ReportStatus from TelemetrySettings. Use componentstatus.ReportStatus instead. (#10777)
  • componentstatus: Make componentstatus.InstanceID immutable. (#10494)

🚩 Deprecations 🚩

  • scraperhelper: deprecate NewObsReport, ObsReport, ObsReportSettings, scrapers should use NewScraperControllerReceiver (#10959)
  • mdatagen: Deprecating generated Meter func in favour of LeveledMeter (#10939)
  • connector: Deprecate connector.Builder, and move it into an internal package of the service module (#10784)
  • exporter: Deprecate exporter.Builder, and move it into an internal package of the service module (#10783)
  • extension: Deprecate extension.Builder, and move it into an internal package of the service module (#10785)
  • processor: Deprecate processor.Builder, and move it into an internal package of the service module (#10782)
  • receiver: Deprecate receiver.Builder, and move it into an internal package of the service module (#10781)

... (truncated)

Commits
  • 02d466f [chore] Prepare release v1.15.0/v0.109.0 (#11101)
  • a269871 Add replace statements for contrib tests (#11100)
  • b18f7cd Add replace statements for builder profiler artifacts (#11097)
  • 32cff9f [chore] update dep to make update-otel in contrib easier (#11089)
  • 0ddedf0 [service] move useOtelWithSDKConfigurationForInternalTelemetry gate to beta (...
  • 6ea5b69 [chore] bump go version (#11090)
  • 46d04a5 [scraperhelper] remove deprecated obsreport funcs/structs (#11086)
  • 3f9bc53 [processorhelper] deprecating unused methods (#11083)
  • 6925a30 [chore]: enable len and empty rules from testifylint (#11021)
  • e599957 Refine scraperhelper.NewScraper to take component.Type directly (#11082)
  • 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[bot] avatar Sep 12 '24 16:09 dependabot[bot]

Regression Detector

Regression Detector Results

Run ID: 6d0de88f-9704-474c-b068-f81ab16025b0 Metrics dashboard Target profiles

Baseline: e0b516c329b4996a08c298057e4631eee3f02a5c Comparison: 00991db518d95ab7ae55f7cedc27827fcdbdd325

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

No significant changes in experiment optimization goals

Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
pycheck_lots_of_tags % cpu utilization +2.25 [-0.28, +4.78] 1 Logs
uds_dogstatsd_to_api_cpu % cpu utilization +1.54 [+0.78, +2.30] 1 Logs
otel_to_otel_logs ingress throughput +0.30 [-0.51, +1.11] 1 Logs
idle memory utilization +0.22 [+0.17, +0.27] 1 Logs
tcp_syslog_to_blackhole ingress throughput +0.16 [+0.11, +0.20] 1 Logs
file_tree memory utilization +0.06 [-0.05, +0.17] 1 Logs
uds_dogstatsd_to_api ingress throughput +0.00 [-0.10, +0.11] 1 Logs
tcp_dd_logs_filter_exclude ingress throughput -0.00 [-0.01, +0.01] 1 Logs
basic_py_check % cpu utilization -3.31 [-6.06, -0.55] 1 Logs

Bounds Checks

perf experiment bounds_check_name replicates_passed
idle memory_usage 10/10

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:

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

pr-commenter[bot] avatar Sep 12 '24 17:09 pr-commenter[bot]

Superseded by #29526.

dependabot[bot] avatar Sep 23 '24 21:09 dependabot[bot]