Bump github.com/open-telemetry/opentelemetry-collector-contrib/receiver/splunkhecreceiver from 0.106.1 to 0.109.0 in /functional_tests

[dependabot]

Bumps github.com/open-telemetry/opentelemetry-collector-contrib/receiver/splunkhecreceiver from 0.106.1 to 0.109.0.

Release notes

Sourced from github.com/open-telemetry/opentelemetry-collector-contrib/receiver/splunkhecreceiver's releases.

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

• clickhouseexporter: Upgrade trace SpanKind and StatusCode string values (#34799) This change updates the output of the trace SpanKind and StatusCode fields to be consistent with the specification's enum values. While this change will not break any deployments, it may affect queries dependent on the old enum names.

  For more details on old->new values, see this related PR: open-telemetry/opentelemetry-collector#6250

• spanmetricsconnector: Improve consistency between metrics generated by spanmetricsconnector. Added traces.span.metrics as default namespace (#33227, #32818) Default namespace for the generated metrics is traces.span.metrics now. | The deprecated metrics are: calls, duration and events. | The feature flag connector.spanmetrics.legacyLatencyMetricNames was added to revert the behavior.

• servicegraphconnector: Fix histogram metrics miss unit (#34511) All metrics will remove the suffix _seconds. It will not introduce breaking change if users use | prometheusexporter or prometheusremotewriteexporter to exporter metrics in pipeline. | In some cases, like using clickhouseexporter(save data in native OTLP format), it will be a breaking change. | Users can use transformprocessor to add back this suffix.

• gitproviderreceiver: The Git Provider Receiver has been renamed to GitHub Receiver. (#34731) This rename was to better match the OpenTelemetry semantic convention changes in v1.27.0 and allows for Traces and Log signals to be added to this component. Traces as mentioned in issue #27460 will be added in a future release to this component.

• ottl: Remove tracing from OTTL due to performance concerns (#34910)

• vcenterreceiver: Updated units on several metrics to be more in line with documented semantics. (#34946) The following are the metrics with their respective unit changes:

  • vcenter.datacenter.cpu.limit ({MHz} -> MHz)
  • vcenter.cluster.cpu.limit ({MHz} -> MHz)
  • vcenter.cluster.cpu.effective ({MHz} -> MHz)
  • vcenter.cluster.vsan.operations ({operations/sec} -> {operations/s})
  • vcenter.cluster.vsan.congestions ({congestions/sec} -> {congestions/s})
  • vcenter.host.network.packet.error.rate ({errors/sec} -> {errors/s})
  • vcenter.host.network.packet.rate ({packets/sec} -> {packets/s})
  • vcenter.host.network.packet.drop.rate ({packets/sec} -> {packets/s})
  • vcenter.host.vsan.operations ({operations/sec} -> {operations/s})
  • vcenter.host.vsan.congestions ({congestions/sec} -> {congestions/s})
  • vcenter.resource_pool.cpu.usage ({MHz} -> MHz)
  • vcenter.vm.network.throughput (By/sec -> By/s)
  • vcenter.vm.network.packet.rate ({packets/sec} -> {packets/s})
  • vcenter.vm.vsan.operations ({operations/sec} -> {operations/s})

🚩 Deprecations 🚩

• instanaexporter: Marking instanaexporter module as deprecated (#34994)

💡 Enhancements 💡

• pkg/ottl: Added Decode() converter function (#32493)

... (truncated)

Changelog

Sourced from github.com/open-telemetry/opentelemetry-collector-contrib/receiver/splunkhecreceiver's changelog.

v0.109.0

🛑 Breaking changes 🛑

• pkg/ottl: Change the OTTL grammar to support expressing statements context via path names (#29017) The ottl.Path interface requires a new method: Context() string
• prometheusreceiver: Move the TargetAllocator configuration struct to an internal directory (#33146)

💡 Enhancements 💡

• pkg/ottl: Add support for localized time parsing into the coreinternal/timeutils (#32977)
• googlecloudmonitoringreceiver: Enhancing the Google Cloud monitoring receiver to establish a client connection, scrape GCP Cloud Metrics, and transform them into an OpenTelemetry compatible format for pipeline processing. (#33762)
  • Implements client connection to Google Cloud Monitoring API.
  • Scrapes timeseries data based on configured metrics.
  • Converts the data into OpenTelemetry format for use in the pipeline.

v0.108.0

🛑 Breaking changes 🛑

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

v0.107.0

🚀 New components 🚀

• googlecloudmonitoringreceiver: Adding new component - Google Cloud monitoring receiver to fetch GCP Cloud Metrics and transform to OpenTelemetry compatible format. (#33762)

💡 Enhancements 💡

• internal/grpcutil: Add internal/grpcutil package with gRPC-specified timeout parsing (#33688)
• pmetrictest: Add support for histogram comparison options (#34521)
• kafkaexporter: add an ability to partition logs based on resource attributes. (#33229)

Commits

• bd98b9d [chore] Prepare release 0.109.0 (#35124)
• 44bc868 [receiver/hostmetrics] respect env var use in filesystem scraper (#35045)
• 0678231 [filestorage] - Add directory validation for compaction on-rebound (#35114)
• ede416f Synchronize shutdown in stanza adapter (#34638)
• 6c9976a [fileconsumer] Fix max_concurrent_files check (#35118)
• 17be441 Update otelcol to latest release 1.15.0 and 0.109.0 (#35093)
• 71ce97e [chore] Fixing Prom Compliance tests (#35071)
• bd66ceb [chore] Update test expectation to include processorhelper metrics (#35073)
• b3e952f [exporter/datadogexporter] Add support for custom log source (#35051)
• 0ceefaa [exporter/datadog] Use correct hostname for logs in logs agent pipeline (#35058)
• 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.