[receiver/vcenter] vcenter.cluster.memory.used Not Implemented

[StefanKurek]

Component(s)

receiver/vcenter

What happened?

Description

Currently, the vcenter.cluster.memory.used is not actually implemented. I verified this by looking at the code.

Steps to Reproduce

Collect against any vCenter environment with an active Cluster.

Expected Result

See the vcenter.cluster.memory.used metric returned for Cluster resources.

Actual Result

No vcenter.cluster.memory.used metric returned for Cluster resources.

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 planning on just gutting this metric ultimately. It doesn't have direct metrics to pull from the API to grab/calculate it. It also doesn't have a CPU equivalent for a Cluster either.

I'll start with adding a warning to the metric about future removal, with a followup PR actually removing it.