Out-of-the-box, the Management Pack for Cloud Federation includes a configuration file named as cloud_federation_config..

The configuration file retrieves the following information.

  • Resources

  • Metrics

  • Properties

With Management Pack for Cloud Federation, you can retrieve a subset of objects from an object type of a child vRealize Operations Cloud instance. The adapter provides a mechanism to filter the subset by either using properties or tags.

The tag-based filter used is:

<Filter> <Tag category="SOME_CATEGORY" name="SOME_TAG" /> </Filter>

The property-based filter used is:

<Filter> <Property attrkey="SOME_KEY" value="SOME_VALUE"/> </Filter>

Note:

You can use only one filter for a given object type, otherwise the configuration file validation will fail.

To create filters for resource kinds, add the filtering element immediately after the resource kind element in the configuration file. For example:

<ResourceKind resourceKindKey="...">
        <Filter>
            <Property attrkey="..." value="..."/>
        </Filter>
        <Metric ..."/>
        <Property .../>
    </ResourceKind>

Types of Configuration Files Used in the Management Pack for Cloud Federation

Default Configuration File

Management Pack for Cloud Federation contains a default configuration file. The Management Pack for Cloud Federation dashboards are based on these configuration files. The default configuration file contains information of vCenter to host level and not VM level. The configuration file also provides information of vCenter operation adapter objects, VMware SDDC Health Monitoring Solution adapter, and VMware Site Recovery Manager adapter.

Note:

The default cloud_federation_config file is aligned with the latest vRealize Operations Cloud. Ensure that the desired metrics/properties from the older versions (which no longer exist in the newer versions) are mentioned in the configuration file.

Heterogeneous Configuration File

You are not limited to using the same configuration file for all adapter instances when you are configuring multiple adapter instances for a separate child of vRealize Operations Cloud instance. You can collect different data from different child vRealize Operations Cloud instances. You can have different level of information in different configuration files.