How-to For: developers, administrators

Monitoring tools

Connect Telegraf, the Prometheus vmware_exporter and Zabbix to the controller through the vSphere endpoints and what was verified for each.

Monitoring tools for vSphere read the inventory and the performance counters through the SOAP endpoint at /sdk. This page is about tools that expect the vSphere API.

Before you start

  • Turn the compatibility endpoints on: Settings of the compatibility endpoints.
  • Create an account for the tool with a role that can read the inventory and the performance data, for example the built-in role Read-only. A monitoring account needs no write privilege.
  • The controller uses a certificate that the tools do not know by default. Trust it, or for a test skip the verification in the tool.

With the CLI

Telegraf, with the vSphere input. The URL is the /sdk address of the controller:

TOML
[[inputs.vsphere]]
  vcenters = ["https://controller.example.com:8443/sdk"]
  username = "monitoring"
  password = "${KYVERNON_MONITORING_PASSWORD}"
  insecure_skip_verify = true

The Prometheus vmware_exporter and the Zabbix VMware monitoring take the address of the controller as the vCenter address, with the port, and the credentials of the account.

Verified

ToolState
Telegraf 1.40.3, vSphere inputVerified. The metric groups for hosts (CPU, memory, network, disk), virtual machines (CPU, memory, network, virtual disk), clusters (CPU, memory) and datastores (disk) were present.
Zabbix 7.0.32, VMware templateNot verified with a Zabbix server. The requests of the Zabbix VMware collector were replayed against the endpoint and answered: service content, sign-in, host properties, the performance counters, a real-time performance query for a host, the event history and sign-out.
Prometheus vmware_exporter 0.18.4Not yet verified.

Only what the table says is verified. The complete list is in verified tools.

Known gaps

  • Values that come from inside the guest, such as the capacity of guest disks, are available only when a guest agent runs.
  • A tool that calls a method that is not served gets a NotSupported fault for that call. The served methods are in supported vSphere API methods.

Version 0.1. Last changed: 2026-11-13