chore(deps): update module go.opentelemetry.io/collector to v0.109.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
go.opentelemetry.io/collector	0.108.1 -> 0.109.0

---

Release Notes

open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector)

v0.109.0

Compare Source

🛑 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
  • otelcol_processor_incoming_log_records
  • otelcol_processor_outgoing_log_records

🧰 Bug fixes 🧰

• configgrpc: Change the value of max_recv_msg_size_mib from uint64 to int to avoid a case where misconfiguration caused an integer overflow. (#​10948)
• exporterqueue: Fix a bug in persistent queue that Offer can becomes deadlocked when queue is almost full (#​11015)

---

Configuration

📅 Schedule: Branch creation - "before 5am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[jburns24]

Strategy for this deps update was the following.

Update the OTEL core beta and stable components to v0.109.0 and v1.15.0 respectively in config/manifests.yaml and go.mod files that referenced these modules. Update the OTEL contrib modules to v0.109.0 in config/manifests.yaml and go.mod files that referenced those modules. Run make tidy-all and make build.

[jburns24]

Upon trying to build I ran into the following OCB error

Error: mismatch in go.mod and builder configuration versions: component "go.opentelemetry.io/collector/confmap/provider/envprovider" version calculated by dependencies "v1.15.0" does not match configured version "v0.109.0". Use --skip-strict-versioning to temporarily disable this check. This flag will be removed in a future minor version
make: *** [build] Error 1

This was fixed by adding the following to our ocb build configuration.

liatrio-otel-collector/config/manifest.yaml

Lines 60 to 61 in 47a44c7

	providers:
	- gomod: go.opentelemetry.io/collector/confmap/provider/envprovider v1.15.0

I could not find what this section does in the builder config but this line was in both the core and contrib builder config and it resolved the build error.

[jburns24]

After building the collector I tested running it and ran into this error

/Users/jburns/git/liatrio-otel-collector/build/otelcol-custom --config config/config.yaml
Error: failed to get config: cannot resolve the configuration: cannot retrieve the configuration: scheme "file" is not supported for uri "file:config/config.yaml"
2024/09/10 15:49:52 collector server run finished with error: failed to get config: cannot resolve the configuration: cannot retrieve the configuration: scheme "file" is not supported for uri "file:config/config.yaml"
make: *** [run] Error 1

On a whim I added the following as I also found it in the contrib and core collector build config.

liatrio-otel-collector/config/manifest.yaml

Line 62 in 47a44c7

- gomod: go.opentelemetry.io/collector/confmap/provider/fileprovider v1.15.0

This resolved the runtime error