[receiver/vcenter] vcenter.vm.disk.throughput Not Implemented

[StefanKurek]

Component(s)

receiver/vcenter

What happened?

Description

I can see in the code that this metric was not actually implemented.

Steps to Reproduce

Collect against any vCenter environment with VMs.

Expected Result

vcenter.vm.disk.throughput is returned for each VM.

Actual Result

No vcenter.vm.disk.throughput metric is returned.

Collector version

v1.6.0/v0.99.0

Environment information

No response

OpenTelemetry Collector configuration

extensions:
  basicauth/prom:
    client_auth:
      username: [PROMUSER]
      password: [PROMPASS]

exporters:
  prometheusremotewrite:
    endpoint: [PROMENDPOINT]
    auth:
      authenticator: basicauth/prom
    resource_to_telemetry_conversion:
      enabled: true # Convert resource attributes to metric labels

processors:
  batch:
    # https://github.com/open-telemetry/opentelemetry-collector/tree/main/processor/batchprocessor

receivers:
  vcenter:
    endpoint: https://[VCENTERHOST]
    username: [VCENTERUSER]
    password: [VCENTERPASS]
    tls:
      insecure: true
    collection_interval: 1m
    initial_delay: 1s

service:
  extensions: [basicauth/prom]
  pipelines:
    metrics:
      receivers: [vcenter]
      processors: [batch]
      exporters: [prometheusremotewrite]

Log output

No response

Additional context

No response

[StefanKurek]

@djaglowski I propose implementing this metric, closely matching the currently implemented vcenter.host.disk.throughput metric. I would change the current metadata so that it is a gauge instead of a non-monotonic cumulative sum though (this is more correct as it is reported as a KB/s rate calculated over 20s).

[github-actions]

Pinging code owners for receiver/vcenter: @djaglowski @schmikei @StefanKurek. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[djaglowski]

Closed by #32780