Stackstate-VMware Integration


  • Get your performance metrics from vSphere and see them all in Stackstate.
  • Get vSphere events in Stackstate and overlay them on top of your metrics (vMotion, configuration changes, on/off…).
  • Interact with your teams on dashboards and the event stream, showing all vSphere data at one glance.



The VMware integration is distributed as a StackPack. Visit the StackPacks page in your StackState installation to install and configure it.


  1. Install the StackState agent on your StackState server, or another server supporting the StackState agent.
  2. Create a StackState user in the Administration section of vCenter, you can use the default Read-Only access group.


  1. Configure the Agent to connect to your vCenter instance. Edit conf.d/vsphere.yaml:

      - name: main-vcenter
        username: stackstate-readonly@vsphere.local
        password: mypassword

  2. Restart the Agent

Configuration Options

  • ssl_verify (Optional) - Set to false to disable SSL verification, when connecting to vCenter optional
  • ssl_capath (Optional) - Set to the absolute file path of a directory containing CA certificates in PEM format
  • host_include_only_regex (Optional) - Use a regex like this if you want only the check to fetch metrics for these ESXi hosts and the VMs running on it
  • vm_include_only_regex (Optional) - Use a regex to include only the VMs that are matching this pattern.
  • include_only_marked (Optional) - Set to true if you’d like to only collect metrics on vSphere VMs which are marked by a custom field with the value ‘StackstateMonitored’. To set this custom field with PowerCLI, use the follow command: Get-VM <MyVMName> | Set-CustomField -Name "StackstateMonitored" -Value "StackstateMonitored"
  • all_metrics (Optional) - When set to true, this will collect EVERY metric from vCenter, which means a LOT of metrics you probably do not care about. We have selected a set of metrics that are interesting to monitor for you if false.
  • event_config (Optional) - Event config is a dictionary. For now the only switch you can flip is collect_vcenter_alarms which will send as events the alarms set in vCenter.


You may need to increase the maxQuerySize parameter in vCenter versions 6.0 and below.


Execute the info command and verify that the integration check has passed. The output of the command should contain a section similar to the following:



      - instance #0 [OK]
      - Collected 8 metrics & 0 events

Data Collected


Milliseconds of extra CPU time.
shown as millisecond
Milliseconds of CPU time spent in ready state.
shown as millisecond
Percentage of CPU capacity being used.
shown as percent
Total megehertz of CPU being used.
shown as megahertz
Number of SCSI commands aborted.
shown as occurrence
Average amount of time it takes to complete an SCSI command from physical device.
shown as millisecond
Average amount of time it takes to complete read from physical device.
shown as millisecond
Average amount of time it takes to complete write to the physical device (LUN).
shown as millisecond
Average amount of time spent in VMkernel queue (per SCSI command).
shown as millisecond
Sum of average amount of time (in kernel and device) to process an SCSI command issued by the Guest OS to the vm.
shown as millisecond
Kilobytes of memory that the VMkernel estimates is being actively used based on recently touched memory pages.
shown as kibibyte
Kilobytes of memory that have been compressed.
shown as kibibyte
Kilobytes of used memory.
shown as kibibyte
Kilobytes of memory allocated to a vm beyond its reserved amount.
shown as kibibyte
Kilobytes of memory allocated by the virtual machine memory control driver (vmmemctl).
shown as kibibyte
Number of kilobytes received by the host.
shown as kibibyte
Number of kilobytes transmitted by the host.
shown as kibibyte