Cloud Cruiser became HPE Consumption Analytics on Nov. 1st. You'll still see the old name in places while we update this site.

 

 

Consumption Analytics Documentation

Home > Cloud Cruiser 3 > Setting Up Collection > Native collectors > VMware vSphere > Perf Collector > Defining perf profiles

Defining perf profiles

You must define a perf profile for each type of managed object for which you want to collect perf data. This profile lists the specific counters to collect for entities of that type.

Properties

For each counter you want to collect, you must specify the following properties in the relevant perf profile. To determine their values, use a counter reference file generated by the collector. This reference, generated by your live system, is more accurate than the list of performance counters in the vSphere API Reference:

  • group: The counter group to which the desired counter belongs. This is the groupInfo.key value in column B.
  • name: The name of the desired counter. This is the nameInfo.key value in column E.
  • rollupType: The type of vSphere data rollup to request for the counter within the samplingPeriod specified in your feed configuration. This is the rollupType value in column K. Valid values are NONE, AVERAGE, MINIMUM, MAXIMUM, SUMMATION, and ​LATEST.
  • function: (optional) If you are aggregating perf data, you must specify the aggregation function to apply to the samples returned. Valid values are MIN , MAX , AVG , and SUM. For more information, see Aggregating perf data. HPE recommends that you align this function with the rollup type to produce consistent aggregation from narrower to broader time intervals.

Together, the group, name, and rollupType values uniquely identify a counter represented by one row in the counter reference file. For example, mem.consumed with average values rolled up.

The cpu.usage counter is intended to represent the percentage of CPU being used, but as of vSphere 5.1 the counter value provided is that percentage multiplied by 100. For example, a cpu.usage value of 1161 means CPU usage of 11.61%. HPE recommends that you divide the collected value by 100 or 10,000 in a transformation step, depending upon how you want to represent it in reports.

vSphere Statistics Level

Each vSphere performance counter specifies a required statistics level, also known as a collection level, for both aggregated data and per-device data. In counter reference files generated by the HPE Consumption Analytics Portal vSphere Perf Collector, these required levels are in the level and perDeviceLevel values in columns M and N. vSphere collects performance data only for the counters whose required aggregated statistics level is met by vSphere's Statistics Level.

If vSphere's ​current Statistics Level isn't high enough to meet the levels required by the performance counters you want to collect, you can address this either by raising the Statistics Level for the interval you're collecting or by lowering the required levels for your desired counters.

Modifying the vSphere level

This is the easier method, though it can affect the performance of your vCenter server.

To modify the vSphere Statistics Interval

  1. Log in to your vCenter server using the vSphere client.
  2. Choose Administration > vCenter Server Settings > Statistics.
  3. In the table, select the interval that equals the samplingPeriod specified in your feed configuration, then click Edit.
    For example, if your samplingPeriod is 7200 seconds, select 2 Hours.
  4. Select a Statistics Level, then click OK twice to save your changes and return to the vSphere window.

Modifying the required level for a counter

It is possible to set the required statistics level for one or more individual performance counters, allowing you to collect performance data without raising the vSphere Statistics Interval. For information about this technique, see this third-party blog post and this VMware knowledge base article.

Example

The following profile tells the collector to collect disk.used with maximum values rolled up, disk.capacity ​with maximum values rolled up, and disk.provisioned with maximum values rolled up for Datastore entities, and that the maximum sample value for each counter is written to the output record when aggregationInterval is other than NONE :

<bean class="com.cloudcruiser.batch.collect.vmware.vsphere.perf.PerfProfile">
  <property name="entityType" value="Datastore" />
  <property name="counters">
    <list>
      <bean class="com.cloudcruiser.batch.collect.vmware.vsphere.perf.Counter">
        <property name="group" value="disk" />
        <property name="name" value="used" />
        <property name="rollupType" value="MAXIMUM"/>
        <property name="function" value="MAX" />
      </bean>
      <bean class="com.cloudcruiser.batch.collect.vmware.vsphere.perf.Counter">
        <property name="group" value="disk" />
        <property name="name" value="capacity" />
        <property name="rollupType" value="MAXIMUM"/>
        <property name="function" value="MAX" />
      </bean>
      <bean class="com.cloudcruiser.batch.collect.vmware.vsphere.perf.Counter">
        <property name="group" value="disk" />
        <property name="name" value="provisioned" />
        <property name="rollupType" value="MAXIMUM"/>
        <property name="function" value="MAX" />
      </bean>
    </list>
  </property>
</bean>
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
© Copyright 2018 Hewlett Packard Enterprise Development LP