build(deps): bump the otel group with 2 updates

[dependabot]

Bumps the otel group with 2 updates: github.com/open-telemetry/opentelemetry-collector-contrib/pkg/translator/jaeger and go.opentelemetry.io/collector/consumer.

Updates github.com/open-telemetry/opentelemetry-collector-contrib/pkg/translator/jaeger from 0.148.0 to 0.149.0

Release notes

Sourced from github.com/open-telemetry/opentelemetry-collector-contrib/pkg/translator/jaeger's releases.

v0.149.0

The OpenTelemetry Collector Contrib contains everything in the opentelemetry-collector release, be sure to check the release notes there as well.

End User Changelog

🛑 Breaking changes 🛑

• exporter/elasticsearch: Remove host.os.type encoding in ECS mode (#46900) Use processor/elasticapmprocessor v0.36.2 or later for host.os.type enrichment
• receiver/prometheus: Remove the deprecated report_extra_scrape_metrics receiver configuration option and obsolete extra scrape metric feature gates. (#44181) report_extra_scrape_metrics is no longer accepted in prometheusreceiver configuration. Control extra scrape metrics through the PromConfig.ScrapeConfigs.ExtraScrapeMetrics setting instead.

🚩 Deprecations 🚩

• receiver/awsfirehose: Deprecate built-in unmarshalers (cwlogs, cwmetrics, otlp_v1) in favor of encoding extensions. (#45830) Use the aws_logs_encoding extension (format: cloudwatch) instead of cwlogs, and the awscloudwatchmetricstreams_encoding extension instead of cwmetrics (format: json) or otlp_v1 (format: opentelemetry1.0).

• receiver/file_log: Rename filelog receiver to file_log with deprecated alias filelog (#45339)

• receiver/kafka: Deprecate the built-in azure_resource_logs encoding in favour of azureencodingextension. (#46267) The built-in azure_resource_logs encoding does not support all timestamp formats emitted by Azure services (e.g. US-format timestamps from Azure Functions). Users should migrate to the azureencodingextension, which provides full control over time formats and is actively maintained.

💡 Enhancements 💡

• cmd/opampsupervisor: Add configuration validation before applying remote config to prevent collector downtime (#41068) Validates collector configurations before applying them, preventing downtime from invalid remote configs. Disabled by default. Enable via agent.validate_config: true. May produce false positives when resources like ports are temporarily unavailable during validation.

• connector/datadog: Document datadog connector is not supported in aix environments (#47010) Explicitly opt out of host metadata computation in datadog components to support AIX compilation target.

• connector/signal_to_metrics: Add keys_expression support in include_resource_attributes and attributes for dynamic attribute key resolution at runtime (#46884) The keys_expression field allows specifying an OTTL value expression that resolves to a list of attribute keys at runtime. This enables dynamic resource attribute filtering based on runtime data such as client metadata. Exactly one of key or keys_expression must be set per entry.

• connector/signal_to_metrics: Reduce per-signal allocations in the hot path by replacing attribute map allocation with a pooled hash-based ID check, and caching filtered resource attributes per metric definition within each resource batch. (#47197)

• connector/signal_to_metrics: Pre-compute prefixed collector key to avoid a string allocation on every signal processed. (#47183) Pre-computing the collector key avoids a string allocation on every signal processed.

• exporter/datadog: Document datadog exporter is not supported in aix environments (#47010) Explicitly opt out of host metadata computation in datadog components to support AIX compilation target.

... (truncated)

Changelog

Sourced from github.com/open-telemetry/opentelemetry-collector-contrib/pkg/translator/jaeger's changelog.

v0.149.0

🛑 Breaking changes 🛑

• pkg/stanza: Change signature of adapter.NewFactory to accept xreceiver.FactoryOptions (#45339) While the change is technically breaking, the existing calls to adapter.NewFactory will continue to work.

💡 Enhancements 💡

• pkg/expohisto: Move Go exponential histogram data structure into collector-contrib repository (#46646)

• receiver/docker_stats: Add TLS configuration support for connecting to the Docker daemon over HTTPS with client and server certificates. (#33557) A new optional tls configuration block is available in docker_stats receiver config (and the shared internal/docker package). When omitted the connection remains insecure (plain HTTP or Unix socket), preserving existing behavior. When provided it supports the standard configtls.ClientConfig fields: ca_file, cert_file, key_file, insecure_skip_verify, min_version, and max_version. A warning is now emitted when a plain tcp:// or http:// endpoint is used without TLS, reflecting Docker's deprecation of unauthenticated TCP connections since Docker v26.0 (see https://docs.docker.com/engine/deprecated/#unauthenticated-tcp-connections).

• receiver/docker_stats: Add "stream_stats" config option to maintain a persistent Docker stats stream per container instead of opening a new connection on every scrape cycle. (#46493) When stream_stats: true is set, each container maintains a persistent open Docker stats stream instead of opening and closing a new connection on every scrape cycle. The scraper reads from the cached latest value, which reduces connection overhead.

• receiver/sqlquery: Add row_condition to metric configuration for filtering result rows by column value (#45862) Enables extracting individual metrics from pivot-style result sets where each row represents a different metric (e.g. pgbouncer's SHOW LISTS command). When row_condition is configured on a metric, only rows where the specified column equals the specified value are used; all other rows are silently skipped.

Commits

• 262df71 [chore] Prepare release 0.149.0 (#47280)
• 4158922 [chore] update dependency (#47273)
• 9a9c779 fix(deps): update module golang.org/x/sync to v0.20.0 (#47266)
• 4c1d5a1 [receiver/mysql] Adding trace propagation (#46327)
• d660724 fix(deps): update module github.com/hetznercloud/hcloud-go/v2 to v2.37.0 (#47...
• 0cee133 fix(deps): update module github.com/stretchr/testify to v1.11.1 (#47263)
• 33d749a fix(deps): update module github.com/googleapis/gax-go/v2 to v2.20.0 (#47260)
• 12912f3 fix(deps): update module github.com/hashicorp/go-version to v1.9.0 (#47261)
• 173558b [chore] [sentryexporter] Add giortzisg to CODEOWNERS (#47258)
• 1647290 [receiver/hostmetrics] restrict system.processes.created to Linux and OpenBSD...
• Additional commits viewable in compare view

Updates go.opentelemetry.io/collector/consumer from 1.54.0 to 1.55.0

Release notes

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

v1.55.0/v0.149.0

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

End User Changelog

🛑 Breaking changes 🛑

• pkg/service: Remove service_name, service_instance_id, and service_version as constant labels on every internal metric datapoint. These attributes are already present in target_info and were being duplicated on each series for OpenCensus backwards compatibility. (#14811) Previously, the collector stamped every internal metric series (e.g. otelcol_process_runtime_heap_alloc_bytes) with service_name, service_instance_id, and service_version labels to match the old OpenCensus behavior. These attributes are now only present in the target_info metric, which is the correct Prometheus/OTel convention. Users who filter or group by these labels on individual metrics will need to update their queries to use target_info joins instead.

💡 Enhancements 💡

• all: Move aix/ppc64 to tier 3 support (#13380)

• all: Upgrade the profiles stability status to alpha (#14817) The following components have their profiles status upgraded from development to alpha:

  • pdata/pprofile
  • connector/forward
  • exporter/debug
  • receiver/nop
  • exporter/nop
  • exporter/otlp_grpc
  • exporter/otlp_http

• cmd/mdatagen: Add semconv reference for attributes (#13297)

🧰 Bug fixes 🧰

• cmd/mdatagen: Fix entity code generation so extra_attributes are emitted as resource attributes instead of entity descriptive attributes. (#14778)

API Changelog

💡 Enhancements 💡

• cmd/mdatagen: Added ability to generate required fields validation to config go structs generated by mdatagen (#14563)

🧰 Bug fixes 🧰

• cmd/mdatagen: Fix RootPackage to use go module root instead of git repo root (#14801) Fixes issue with running mdatagen when the git repository root is different from the go module root.

... (truncated)

Changelog

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

v1.55.0/v0.149.0

💡 Enhancements 💡

• cmd/mdatagen: Added ability to generate required fields validation to config go structs generated by mdatagen (#14563)

🧰 Bug fixes 🧰

• cmd/mdatagen: Fix RootPackage to use go module root instead of git repo root (#14801) Fixes issue with running mdatagen when the git repository root is different from the go module root.

Commits

• 01b07fc [chore] Prepare release v1.55.0/v0.149.0 (#15033)
• 4d17eb8 Update All golang.org/x packages (#14994)
• a58f96f Update module github.com/klauspost/compress to v1.18.5 (#14991)
• 85f1268 [chore][mdatagen] Fix metrics test bug with resource attributes (#15008)
• 6a56478 [mdatagen] Add semconv reference for attributes in metadata schema (#14646)
• 9860d1b [chore] Update release schedule (#15013)
• 2f66cc6 Update module github.com/knadh/koanf/v2 to v2.3.4 (#14992)
• 3e733d0 Update module go.opentelemetry.io/otel to v1.42.0 (#14997)
• dccf5c6 hore: remove MD018 markdownlint exception (#15005)
• ba01037 [chore] Fix config validation generation to be deterministic (#15015)
• 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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.