Problem

When using StackState agent 2.10 with the vSphere integration, no metrics are shown for vSphere components in StackState.

Cause

The vSphere check shipped with StackState Agent 2.10 contains an incompatibility with the recent versions of the vSphere StackPack. The vSphere metrics are collected and sent to StackState, but a different metric name is used than that expected by the vSphere StackPack.

Solution

The vSphere check can be configured to use compatible metric names. To enable this feature, configure the all_metrics flag in the vSphere check conf.yaml:

# Section used for global vsphere check config
init_config:

# Define your list of instances here
# each item is a vCenter instance you want to connect to and
# fetch metrics from
instances:
  # name must be a unique key representing your vCenter instance
  # mandatory
  - name: main-vcenter

    # the host used to resolve the vCenter IP
    # mandatory
    host: vcenter.domain.com

    # Read-only credentials to connect to vCenter
    # mandatory
    username: stackstate-readonly@vsphere.local
    password: mypassword

    # 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
    all_metrics: false

With this setting in place, restart the StackState Agent.

vSphere telemetry should now appear in your StackState instance.