build(deps): bump github.com/open-telemetry/opentelemetry-collector-contrib/pkg/translator/jaeger from 0.107.0 to 0.108.0 in the jaeger group

[dependabot]

Bumps the jaeger group with 1 update: github.com/open-telemetry/opentelemetry-collector-contrib/pkg/translator/jaeger.

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

Release notes

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

v0.108.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 🛑

• all: Added support for go1.23, bumped the minimum version to 1.22 (#34658)

• lokiexporter: Update the scope name for telemetry produced by the lokiexporter from otelcol/loki to github.com/open-telemetry/opentelemetry-collector-contrib/exporter/lokiexporter (#34612)

• azuretranslator: The scope name has been updated from otelcol/azureresourcelogs and otelcol/azureresourcetraces to github.com/open-telemetry/opentelemetry-collector-contrib/pkg/translator/azure (#34712)

• datadogreceiver: The scope name has been updated from otelcol/datadogreceiver to github.com/open-telemetry/opentelemetry-collector-contrib/receiver/datadogreceiver/internal/translator (#34711)

• splunkhecexporter: The scope name has been updated from otelcol/splunkhec to github.com/open-telemetry/opentelemetry-collector-contrib/exporter/splunkhecexporter (#34710)

• googlecloudmonitorreceiver: The scope name has been updated from otelcol/googlecloudmonitoringreceiver to github.com/open-telemetry/opentelemetry-collector-contrib/receiver/googlecloudmonitoringreceiver (#34709)

• elasticsearchexporter: Update OTel mapping mode for logs and metrics; Remove trace_flags (#34472) Update logs and metrics OTel mapping mode to always emit "scope" and zero int, but not emit empty strings for known fields. Breaking change to remove trace_flags from logs.

• elasticsearchexporter: Change default retry.retry_on_status to [429] (#32584) To retain the previous behavior, set retry.retry_on_status to [429, 500, 502, 503, 504].

• gitproviderreceiver: Update metric names and attributes to match the newest Semantic Conventions for VCS. (#34278) Attribute Changes:

  • branch.name is now ref.name
  • Added a ref.type attribute
  • pull_request.state is now change.state
  • git.vendor.name is now vcs.vendor.name Metric Changes:
  • git.repository.count is now vcs.repository.count
  • git.repository.contributor.count is now vcs.repository.contributor.count
  • git.repository.branch.count is now vcs.repository.ref.count
  • git.repository.branch.time is now `vcs.repository.ref.time
  • git.repository.branch.commit.aheadby.count is now vcs.repository.ref.revisions_ahead
  • git.repository.branch.commit.behindby.count is now `vcs.repository.ref.revisions_behind
  • git.repository.branch.line.addition.count is now vcs.repository.ref.lines_added
  • git.repository.branch.line.deletion.count is now vcs.repository.ref.lines_deleted
  • git.repository.pull_request.time_open is now vcs.change.time_open
  • git.repository.pull_request.time_to_merge is now vcs.change.time_to_merge
  • git.repository.pull_request.time_to_approval is now vcs.change.time_to_approval
  • git.repository.pull_request.count is now vcs.change.count

• transformprocessor: Promote processor.transform.ConvertBetweenSumAndGaugeMetricContext feature flag from alpha to beta (#34567)

• exporter/datadog: The logs::dump_payloads config option is invalid when the Datadog Agent logs pipeline is enabled (now enabled by default). (#34420) An error will be raised if logs::dump_payloads is set while the Datadog Agent logs pipeline is enabled. To avoid this error, remove the logs::dump_payloads config option or temporarily disable the exporter.datadogexporter.UseLogsAgentExporter feature gate.

• vcenterreceiver: Several host performance metrics now return 1 data point per time series instead of 5. (#34708) The 5 data points previously sent represented consecutive 20s sampling periods. Depending on the collection interval these could easily overlap. Sending just the latest of these data points is more in line with other performance metrics.

  This change also fixes an issue with the googlecloud exporter seeing these datapoints as duplicates.

  Following is the list of affected metrics which will now only report a single datapoint per set of unique attribute values.

  • vcenter.host.cpu.reserved
  • vcenter.host.disk.latency.avg
  • vcenter.host.disk.latency.max

... (truncated)

Changelog

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

v0.108.0

🛑 Breaking changes 🛑

• pkg/stanza/operator/input/windows: Change type name from EvtRpcLogin to EvtRPCLogin. (#34656)

Commits

• 3a3b701 [chore] Prepare release 0.108.0 (#34891)
• 31adabb [chore] update core to v1.14.1/v0.108.1 (#34883)
• f3948de Update module github.com/prometheus/prometheus to v0.54.1 (#34873)
• e790879 Update All github.com/datadog packages (#34854)
• 6831ed1 Update module github.com/elastic/go-structform to v0.0.12 (#34857)
• 18d21a8 Update module github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common...
• dfd6ced Update module github.com/Azure/go-amqp to v1.1.0 (#34864)
• fae484c Update module google.golang.org/api to v0.194.0 (#34869)
• 5b2cd87 Update module go.etcd.io/bbolt to v1.3.11 (#34862)
• ec83b46 [exporter/doris] New component: Doris Exporter (#33790)
• 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 <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]

The group that created this PR has been removed from your configuration.