chore(deps): bump go.opentelemetry.io/collector/pdata from 1.62.0 to 1.63.0 in the opentelemetry group

[dependabot]

Bumps the opentelemetry group with 1 update: go.opentelemetry.io/collector/pdata.

Updates go.opentelemetry.io/collector/pdata from 1.62.0 to 1.63.0

Release notes

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

v1.63.0/v0.157.0

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

End User Changelog

🛑 Breaking changes 🛑

• pkg/exporterhelper: Replace histogram bucket boundaries for otelcol_exporter_queue_batch_send_size_bytes and otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads, and otelcol_exporter_queue_batch_send_size_bytes topped out at 6000 bytes so nearly all observations fell into the +Inf overflow bucket. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the two metrics directly comparable on the same dashboards. Dashboards or alerts that hard-code specific le values for these histograms will need to be updated.

• processor/batch: Replace histogram bucket boundaries for otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the metric directly comparable with otelcol_exporter_queue_batch_send_size_bytes on the same dashboards. Dashboards or alerts that hard-code specific le values for this histogram will need to be updated.

💡 Enhancements 💡

• all: Bootstrap config.schema.yaml for core components (debug/otlp/otlphttp exporters, otlp receiver, batch/memory_limiter processors, memory_limiter/zpages extensions). Implements Phase 1 of the component configuration schema roadmap RFC. (#14543) Schemas are generated using the schemagen tool from opentelemetry-collector-contrib and hand-tuned to capture validation rules and references to shared library schemas (confighttp, configgrpc, configretry, exporterhelper, etc.). A .schemagen.yaml settings file and a generate-schemas Makefile target are added so the schemas can be regenerated reproducibly.

• pkg/service: Apply experimental service::telemetry::resource::detection/development resource detection to the Collector's internal telemetry resource. (#14311) This follows the OpenTelemetry configuration schema by treating service::telemetry::resource::detection/development::detectors as detector selection. Currently supported detector entries are container, host, process, and service. See the OpenTelemetry Configuration Go support table and search for ExperimentalResourceDetector for current detector support: https://github.com/open-telemetry/opentelemetry-configuration/blob/main/language-support-status.md#go

  Example:

  service:
    telemetry:
      resource:
        attributes:
          - name: foo
            value: bar
        detection/development:

... (truncated)

Changelog

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

v1.63.0/v0.157.0

🛑 Breaking changes 🛑

• pkg/config/configgrpc: Remove the BalancerName function (#9477) Use the DefaultBalancerName constant instead.

🚩 Deprecations 🚩

• pkg/xconfmap: Deprecate WithForceUnmarshaler option. (#15614) Use confmap.WithForceUnmarshaler instead.

🚀 New components 🚀

• pkg/config/configstorage: Add a new configstorage module to support storage configuration fields. (#5832)

💡 Enhancements 💡

• pkg/confmap: Add WithForceUnmarshaler option. (#15614) This option allows forcing the top-level Unmarshal method even if the Conf is already a parameter from an Unmarshal method. See the Godoc for more details.

Commits

• 4908404 [chore] Prepare release v1.63.0/v0.157.0 (#15624)
• c823638 [service] chore: Forward hostcapabilities interfaces through extension host...
• 1a861f0 [confmap] Stabilize WithForceUnmarshaler (#15614)
• 7d0e3a0 [configgrpc] Remove the BalancerName function (#15611)
• bd0d94a [configgrpc] Apply WaitForReady option (#15615)
• 3294e3d [chore][configgrpc] Remove direct dependency on xconfmap (#15612)
• 6885b26 [chore][configgrpc] Return correct error when PerRPCCredentials fails (#15616)
• b873893 [chore][configgrpc] Remove duplicate omitempty tag (#15610)
• 2ab65ae [service] Record status events reported by extensions (#15557)
• fa69e2c [service] Fix startup panic when a resource detector emits a slice-valued att...
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 54.24%. Comparing base (2d6070c) to head (fde683a).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #293      +/-   ##
==========================================
+ Coverage   54.11%   54.24%   +0.12%     
==========================================
  Files          29       29              
  Lines        1615     1615              
==========================================
+ Hits          874      876       +2     
+ Misses        708      707       -1     
+ Partials       33       32       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.