Bump go.opentelemetry.io/collector/semconv from 0.104.0 to 0.109.0

[dependabot[bot]]

Bumps go.opentelemetry.io/collector/semconv from 0.104.0 to 0.109.0.

Release notes

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

cmd/builder/v0.106.1

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

v0.106.1

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

End User Changelog

v0.106.1

🧰 Bug fixes 🧰

• configauth: Fix unmarshaling of authentication in HTTP servers. (#10750)

cmd/builder/v0.106.0

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

v0.106.0

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

End User Changelog

v0.106.0

🛑 Breaking changes 🛑

• service: Update all metrics to include otelcol_ prefix to ensure consistency across OTLP and Prometheus metrics (#9759) This change is marked as a breaking change as anyone that was using OTLP for metrics will see the new prefix which was not present before. Prometheus generated metrics remain unchanged.

• confighttp: Delete ClientConfig.CustomRoundTripper (#8627) Set (*http.Client).Transport on the *http.Client returned from ToClient to configure this.

• confmap: When passing configuration for a string field using any provider, use the verbatim string representation as the value. (#10605, #10405) This matches the behavior of ${ENV} syntax prior to the promotion of the confmap.unifyEnvVarExpansion feature gate to beta. It changes the behavior of the ${env:ENV} syntax with escaped strings.

• component: Adds restrictions on the character set for component.ID name. (#10673)

• processor/memorylimiter: The memory limiter processor will no longer account for ballast size. (#10696) If you are already using GOMEMLIMIT instead of the ballast extension this does not affect you.

• extension/memorylimiter: The memory limiter extension will no longer account for ballast size. (#10696) If you are already using GOMEMLIMIT instead of the ballast extension this does not affect you.

• service: The service will no longer be able to get a ballast size from the deprecated ballast extension. (#10696) If you are already using GOMEMLIMIT instead of the ballast extension this does not affect you.

🚀 New components 🚀

• client: Create a new go module go.opentelemetry.io/collector/client (#9804) This module contains generic representations of clients connecting to different receivers.

... (truncated)

Changelog

Sourced from go.opentelemetry.io/collector/semconv'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 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)

[pr-commenter[bot]]

Regression Detector

Regression Detector Results

Run ID: e03fead0-a30d-4157-befd-b4694d0468fb Metrics dashboard Target profiles

Baseline: f6752d3af65c368d68f69c3e32850d1eb74ac10d Comparison: 53241d3f49dccb62a6d2535e7ad68c3527a25a01

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
➖	basic_py_check	% cpu utilization	+0.75	[-1.94, +3.44]	1	Logs
➖	otel_to_otel_logs	ingress throughput	+0.72	[-0.09, +1.52]	1	Logs
➖	idle	memory utilization	+0.44	[+0.38, +0.49]	1	Logs
➖	file_tree	memory utilization	+0.04	[-0.09, +0.18]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.01, +0.01]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.01	[-0.12, +0.11]	1	Logs
➖	pycheck_lots_of_tags	% cpu utilization	-0.06	[-2.56, +2.44]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.08	[-0.14, -0.03]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.66	[-1.39, +0.07]	1	Logs
➖	idle_all_features	memory utilization	-2.17	[-2.30, -2.05]	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".

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.