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 4 > Collecting, transforming, and publishing > XML > Collector properties

Collector properties

Table of contents
No headers

This article explains the XML File Properties that you set in the Edit Collection wizard. In version 4.0 there were no XML File Properties to set.

In version 4.1 and later, those properties are:

  • Name Depth: The number of levels of an input element's fully-qualified name to use in its label when HPE Consumption Analytics Portal generates the default output field mappings for a collection. More levels included means more context in the names of dimensions and measures, but also longer names. For example, for an input element named service.server.name a Name Depth of 1 results in the label name. A Name Depth of 2 results in the label server.name. The default is 2. Of course, you can change these labels to whatever you want.
    If this setting causes a name conflict, numerals are appended to the labels after the first occurrence. For example, name, name2, name3, and so on. Setting Name Depth to 0 is not recommended: this causes all names to be NULL and conflict with each other, producing the label values NULL, 2, 3, and so on.

    You must set Name Depth before either finishing the Create Collection wizard or opening Advanced Configuration. The automatic output field mappings that this setting affects are created when you do either of these things for the first time, so any changes to the setting after that have no effect.

  • Ignore Root: Whether to ignore all elements at the first, or root, level of the XML document both when automatically creating the default Advanced Configuration settings and when running the collection. Because the XML Collector must read to the bottom of the hierarchy for an element at a given level in the document in a single memory operation, a document where everything is contained by a root element can slow down performance or even crash the collector. When you have such a document and the root element contains no attributes that are of value, set this option to Yes to allow the collector to read the elements at the next level individually. The following abbreviated example XML document is a good candidate for using Ignore Root.

    Changing the setting of Ignore Root after the default Advanced Configuration settings have been created will cause XPath expressions to fail because they are generated based on whether the collector is expected to ignore the root element when it runs. If you need to change this setting, also click Reset to Default in the Advanced Configuration dialog box to create XPath expressions that align with the new setting. You might need to modify the expressions or their output mappings from there.

 

<?xml version="1.0" encoding="UTF-8"?>
<documentSet>
    <document>
        <custName>AAA</custName>
        <virtualMachines>
            <virtualMachine>
                <vmName>My VM</vmName>
                <vmId>33663366_9770</vmId>
                <hostName>a host name</hostName>
                <osType>LINUX</osType>
                <osName>Ubuntu (64)</osName>
                <imageType>small</imageType>
                <state>ON</state>
                <ramAllocatedGB>4</ramAllocatedGB>
                <ramReservedGB>4</ramReservedGB>
                <cpuAllocated>1</cpuAllocated>
                <cpuReserved>1</cpuReserved>
                <osPartitionGB>40</osPartitionGB>
                <storage>
                    <virtualDisks>
                        <virtualDisk>
                            <diskName>Disk1</diskName>
                            <diskAllocatedGB>200</diskAllocatedGB>
                            <diskReservedGB>400</diskReservedGB>
                            <fullName>P2000-iscsi/vd01/DL380G7-010-VD01</fullName>
                        </virtualDisk>
                    </virtualDisks>
                </storage>
                <networks>
                    <network>
                        <networkName>VM Network</networkName>
                        <interfaces>
                            <interface>
                                <ipAddress>10.10.0.27</ipAddress>
                            </interface>
                        </interfaces>
                    </network>
                </networks>
            </virtualMachine>
        </virtualMachines>
    </document>
    <document>
        <custName>BBB</custName>
        <virtualMachines>
            <virtualMachine>
                <vmName>My VM</vmName>
                <vmId>55665566_6220</vmId>
                <hostName>another host name</hostName>
                <osType>LINUX</osType>
                <osName>Ubuntu (64)</osName>
                <imageType>medium</imageType>
                <state>ON</state>
                <ramAllocatedGB>8</ramAllocatedGB>
                <ramReservedGB>8</ramReservedGB>
                <cpuAllocated>2</cpuAllocated>
                <cpuReserved>2</cpuReserved>
                <osPartitionGB>80</osPartitionGB>
                <storage>
                    <virtualDisks>
                        <virtualDisk>
                            <diskName>Disk1</diskName>
                            <diskAllocatedGB>400</diskAllocatedGB>
                            <diskReservedGB>400</diskReservedGB>
                            <fullName>P2000-iscsi/vd01/DL380G7-010-VD05</fullName>
                        </virtualDisk>
                    </virtualDisks>
                </storage>
                <networks>
                    <network>
                        <networkName>VM Network</networkName>
                        <interfaces>
                            <interface>
                                <ipAddress>10.10.0.28</ipAddress>
                            </interface>
                        </interfaces>
                    </network>
                </networks>
            </virtualMachine>
        </virtualMachines>
    </document>
</documentSet>
Last modified

Tags

Classifications

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