Infrastructure Integration

Configuration

1. Configure the agent by editing /etc/nutanix/epoch-dd-agent/conf.d/vsphere.yamlin the collectors. Example:

   # 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: username
       password: mypassword
   
       # Set to false to disable SSL verification, when connecting to vCenter
       # optional
       # ssl_verify: true
   
       # Set to the absolute file path of a directory containing CA certificates
       # in PEM format
       # optional
       # ssl_capath: "/path/to/directory"
   
       # Use a regex like this if you want only the check
       # to fetch metrics for these ESXi hosts and the VMs
       # running on it
       # optional
   
       # Use a regex to include only the VMs that are
       # matching this pattern.
       # optional
   
       # optional
       # include_only_marked: false
   
       # 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
       # optional
       # all_metrics: false # /!\ will generate a lot of metrics
   
       # 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
       # event_config:
       #   collect_vcenter_alarms: true # defaults to false
   

2. Check and make sure that all yaml files are valid with following command:

   /etc/init.d/epoch-collectors configcheck
   

3. Restart the Agent using the following command:

   /etc/init.d/epoch-collectors restart
   

4. Execute the info command to verify that the integration check has passed:

   /etc/init.d/epoch-collectors info
   

The output of the command should contain a section similar to the following:

    Checks
    ======

      [...]

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

Infrastructure Datasources

Datasource	Available Aggregations	Unit	Description
vsphere.cpu.extra	avg max min sum	millisecond	Milliseconds of extra CPU time.
vsphere.cpu.ready	avg max min sum	millisecond	Milliseconds of CPU time spent in ready state.
vsphere.cpu.usage	avg max min sum	percent	Percentage of CPU capacity being used.
vsphere.cpu.usagemhz	avg max min sum	megahertz	Total megehertz of CPU being used.
vsphere.disk.commandsAborted	avg max min sum	occurrence	Number of SCSI commands aborted.
vsphere.disk.deviceLatency	avg max min sum	millisecond	Average amount of time it takes to complete an SCSI command from physical device.
vsphere.disk.deviceReadLatency	avg max min sum	millisecond	Average amount of time it takes to complete read from physical device.
vsphere.disk.deviceWriteLatency	avg max min sum	millisecond	Average amount of time it takes to complete write to the physical device (LUN).
vsphere.disk.queueLatency	avg max min sum	millisecond	Average amount of time spent in VMkernel queue (per SCSI command).
vsphere.disk.totalLatency	avg max min sum	millisecond	Sum of average amount of time (in kernel and device) to process an SCSI command issued by the Guest OS to the vm.
vsphere.mem.active	avg max min sum	kibibyte	Kilobytes of memory that the VMkernel estimates is being actively used based on recently touched memory pages.
vsphere.mem.compressed	avg max min sum	kibibyte	Kilobytes of memory that have been compressed.
vsphere.mem.consumed	avg max min sum	kibibyte	Kilobytes of used memory.
vsphere.mem.overhead	avg max min sum	kibibyte	Kilobytes of memory allocated to a vm beyond its reserved amount.
vsphere.mem.vmmemctl	avg max min sum	kibibyte	Kilobytes of memory allocated by the virtual machine memory control driver (vmmemctl).
vsphere.network.received	avg max min sum	kibibyte	Number of kilobytes received by the host.
vsphere.network.transmitted	avg max min sum	kibibyte	Number of kilobytes transmitted by the host.