Bump go.opentelemetry.io/collector/pdata from 1.17.0 to 1.19.0

[dependabot]

Bumps go.opentelemetry.io/collector/pdata from 1.17.0 to 1.19.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.19.0/v0.113.0

🛑 Breaking changes 🛑

• builder: Remove deprecated flags from Builder (#11576) Here is the list of flags | --name, --description, --version, --otelcol-version, --go, --module

🚀 New components 🚀

• processorhelperprofiles: Add processorhelperprofiles to support profiles signal (#11556)

💡 Enhancements 💡

• mdatagen: Add newTelemetrySettings to be generated all the time even for pkg class (#11535)
• debugexporter: Add profiles support to debug exporter (#11155)
• component: Add UnmarshalText for StabilityLevel (#11520)

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

... (truncated)

Commits

• 3da496b [chore] Prepare release v1.19.0/v0.113.0 (#11609)
• 642f473 [chore] add the missing replace in core.builder.yaml (#11604)
• 3b7f68d [chore] fix: pin markdown-link-check to v3.12.2 (#11605)
• b287f60 fix(deps): update module github.com/fsnotify/fsnotify to v1.8.0 (#11598)
• 138f60e fix(deps): update module github.com/shirou/gopsutil/v4 to v4.24.10 (#11597)
• 084aa63 Update builder default providers to lastest stable (#11566)
• 27bcaf6 Apply default values before we unmarshal the config, allows not using pointer...
• bfa1dc5 updated grpc config to use DialContext (#11575)
• 9ae29a8 Remove builder support to build old version, and the otelcol_version config (...
• 69e7a40 (batchprocessor): Move single shard batcher creation to the constructor (#11594)
• 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)

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: f50140b2-a30b-4555-b60b-a109c80f2a00

Baseline: 87e6528
Comparison: 368ddc0
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	pycheck_lots_of_tags	% cpu utilization	+1.32	[-2.06, +4.70]	1	Logs
➖	otel_to_otel_logs	ingress throughput	+0.96	[+0.25, +1.66]	1	Logs
➖	file_tree	memory utilization	+0.96	[+0.83, +1.09]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.66	[-0.06, +1.38]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	+0.03	[-0.46, +0.52]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	+0.01	[-0.17, +0.20]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.01	[-0.23, +0.25]	1	Logs
➖	basic_py_check	% cpu utilization	+0.01	[-3.76, +3.77]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.03	[-0.12, +0.07]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.03	[-0.36, +0.30]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.10	[-0.58, +0.38]	1	Logs
➖	quality_gate_idle	memory utilization	-0.10	[-0.16, -0.05]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.53	[-0.66, -0.41]	1	Logs bounds checks dashboard
➖	tcp_syslog_to_blackhole	ingress throughput	-0.58	[-0.64, -0.53]	1	Logs

Bounds Checks: ❌ Failed

perf	experiment	bounds_check_name	replicates_passed	links
❌	quality_gate_idle	memory_usage	5/10	bounds checks dashboard
❌	file_to_blackhole_0ms_latency	lost_bytes	9/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
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard

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]

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