-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Closed
Labels
Description
Component(s)
receiver/vcenter
What happened?
Description
Currently, the metric vcenter.cluster.memory.effective
appears to be reporting a value in MiB rather than bytes as the metadata of the receiver suggests. This is backed up by the documentation here.
Steps to Reproduce
Collect against any vCenter environment with an active Cluster.
Expected Result
The vcenter.cluster.memory.effective
metric would be returned for Cluster resources with the value representing a number of bytes.
Actual Result
The vcenter.cluster.memory.effective
metric is returned for Cluster resources with the value representing a number of MiB.
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