Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[receiver] vcenter - Multiple datacenters causes failures to collect Resource Pools, vApps, & VMs #33734

Open
StefanKurek opened this issue Jun 24, 2024 · 1 comment
Labels
bug Something isn't working needs triage New item requiring triage receiver/vcenter

Comments

@StefanKurek
Copy link
Contributor

Component(s)

receiver/vcenter

What happened?

Description

Currently when collecting against an environment which contains multiple Datacenters, there is an issue with two of the client calls (ResourcePoolInventoryListObjects and VAppInventoryListObjects). The underlying govmomi client can only handle a default datacenter for these calls, and therefore only resources for 1 datacenter are being returned. This has a side effect of VMs not being created for the non returned objects as well.

Steps to Reproduce

Collect against an environment with multiple datacenters.

Expected Result

Collect metrics for resources under each datacenter.

Actual Result

Many metrics are failed to be created with errors in the logs.

Collector version

v0.102.0

Environment information

No response

OpenTelemetry Collector configuration

No response

Log output

No response

Additional context

No response

Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage New item requiring triage receiver/vcenter
Projects
None yet
Development

No branches or pull requests

2 participants