[vcenterreceiver] standalone ESXi not working #33073
Comments
suprnova1
added
bug
|
Pinging code owners for receiver/vcenter: @djaglowski @schmikei @StefanKurek. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
Taking a look into this now |
|
@djaglowski This did made me double check the current state of the client to see if any other client calls could cause failures like this. Most of the client calls have been updated to a new method, which don't automatically return errors on empty results. There are still two client calls which intentionally use the older methods and do return these errors at the moment. One for resource pool paths and one for virtual app paths. Resource Pools should always exist (there is something very wrong if they do not), but it's very reasonable that Virtual Apps might not exist in an environment. I have a PR which modifies the Virtual App method to ignore the error if it is a |
…l Apps (#33102) **Description:** <Describe what has changed.> Virtual Apps might not exist in an environment. Currently a `NotFound` error for the internal client is thrown when this condition occurs. I modified this to simply return an empty array, because this should simply mean that it did not find any Virtual Apps. I also added more client unit tests to test for these types of conditions. **Link to tracking Issue:** <Issue number if applicable> #33073 (loosely tied to this. At the very least this issue made me discover this problem) **Testing:** <Describe what testing was performed and which tests were added.> Added new unit tests which showed the error. Fix caused the new unit test to pass. **Documentation:** <Describe the documentation added.> N/A
|
@suprnova1 Hello! Are you sure that you're using v0.100.0 of the collector? Looking at the error message you posted, it definitely seems like you're using an older version. If you can verify this, using the newest version of the collector should solve your problem. Let me know. Thanks! |
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
No response
What happened?
As per documentation "This receiver fetches metrics from a vCenter or ESXi host running VMware vSphere APIs."
However, because there is no cluster within standalone ESXi, I receive the following error:
level=error msg="Error scraping metrics" component_path=/ component_id=otelcol.receiver.vcenter.default error="unable to get cluster lists: cluster '*' not found" scraper=vcenter
Collector version
v0.100.0
Environment information
No response
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: