Using Data-Driven Web Services › How to Create a Custom Metric Family › Create a Custom Metric Family XML File › Add the <ComponentList> Section

Add the <ComponentList> Section

A component is an item that is associated with a device (for example, a device can be associated with CPUs, interfaces, and process components). Using the component type helps you categorize the items that are associated with a device. In a metric family, table attributes require a list of the associated components. For components that do not currently exist in Data Aggregator, your metric family XML must also define these new components.

The component information in your metric family XML file serves the following two purposes:

• Discovery—When discovery creates items for a device, the component value identifies a category (facet) for the item.
• Synchronization—During synchronization between Data Aggregator and CA Performance Center, the component definition maps the items, and it determines how they appear in the interface.

In the <ComponentList> section, list the facets you want to create for any component items that are associated with your custom metric family. For example, a metric family that collects process metrics is associated with a device that is running processes. We can define a "process" facet in this section, as follows:

<Component>{namespace}Process</Component>

This example indicates that all items created for our processes metric family are categorized as a "process" component.

Important! Each component listed in this section must be defined in Data Aggregator. If a component is not defined by default in Data Aggregator, define it in the <ComponentDefinitionList> section.

Note: For more information about each XML tag, see the inline documentation provided in the MetricFamily.xsd and Component.xsd files. For code examples, see the ProcessInfoMFWithComponent.xml file. This example file defines a metric family for gathering process metrics.

More information:

Create a Custom Metric Family XML File