Skip to main content
Needs Votes

Missing model in the VMware 8 connector

Related products:Infra Monitoring - Connectors
  • March 23, 2026
  • 4 replies
  • 36 views

Forum|alt.badge.img+8

Hello!!

After contacting support to inquire about the roadmap for VMware 8 connectors, they advised us to post our requirements on The Watch, so here goes:

  • Persona :
    For everyone

  • Problem to solve :
    Ensure that the same checks are performed as with connector 7 when switching to connector 8

  • Expected outcome :
    ESX-HEALTH, ESX-ALARMS, ESX-STATUS, ESX-STORAGE…

Thank you

4 replies

Forum|alt.badge.img+13

I known there is still active work being done on the VMWare 8 Connector, maybe see if you find solutions here 

 


lpinsivy
Centreonian
Forum|alt.badge.img+21
  • Centreonian
  • April 3, 2026
NewNeeds Votes

ltirand
Centreonian
Forum|alt.badge.img+10
  • Centreonian
  • April 17, 2026

Hello :)

We developed the VMware 8 connector based on the understanding and information available in the API (which is significantly less extensive than what was accessible via the Perl SDK in previous versions). If you have the API endpoints that allow you to retrieve the information you require, could you please provide them to us? We would be delighted to enhance this connector if you have this information.

Best regards.


Forum|alt.badge.img+13

How about the python sdk that is still maintained by the broadcom vmware team ? It does connect to the inner SOAP endpoints and gather a lot of data like the perl sdk did.

I tried to use it, not going to lie it’s a pain, but it is a bit more extensive that the REST APIs that in addition vary a lot depending on the version of vsphere.