To access the Hierarchy rules page via Administration tab, click Data Warehouse and then click Hierarchy rules. This page allows you to view the existing hierarchy rules and define new ones. To review the definition of hierarchy, see Hierarchies.
For more information, refer to the following sections:
A hierarchy rule is a condition that selects the set of entities to which a hierarchy template should be applied.
Hierarchy rules and hierarchy templates are used by TrueSight Capacity Optimization to manage hierarchies, and can automatically update hierarchies when new entities and data series are loaded into the Data Warehouse.
For example, a hierarchy rule can dictate that the Virtual Machine template should be applied to all entities of type Virtual Host within the Virtualized Systems domain.
The Hierarchy rules table lists all the currently configured rules (excluding, by default, derived and aggregate rules) and their status, allowing you to perform the following tasks:
Example of the Hierarchy rules page
To add a new hierarchy rule, perform the following task:
Navigate to Administration > DATA WAREHOUSE > Hierarchy rules.
Click Add Rule.
Specify the following details in the Add hierarchy rule page:
|Name||Enter a name for the new hierarchy rule.|
|Description||Enter a brief description for this hierarchy rule.|
|Hierarchy template||Select a hierarchy template from the list. For more information on templates, see Predefined hierarchy templates.|
|Template description||By default, this field is populated based on the selected hierarchy template.|
|Systems and Business drivers filter|
Select All systems and business drivers, Limit to a domain, or Limit to a domain and its children. By default, Limit to a domain is selected.
If you chose Limit to a domain or Limit to a domain and its children, specify a domain in the Domains field.
|Add created objects to||Select an object from Source and click >> to move it to Selection. Click Apply.|
|Share lookup||Select a lookup from the list, if you want to share a lookup with the hierarchy rule.|
|Datasource filter||Select a datasource filter.|
On the hierarchy rules detail page, perform one of the following actions to activate or deactivate a hierarchy rule:
Clickand click OK to deactivate the hierarchy rule. A notification regarding the deactivation is displayed at the top of the Hierarchy rules table.
Deleting a hierarchy rule deletes the defined relationships, but not the derived systems and their data. Deactivating a hierarchy rule stops the derivation of new samples, i.e. samples with a time stamp later than the disable date.
On the hierarchy rules detail page, click Run hierarchy log details.in the appropriate row to run the hierarchy rule. A notification regarding this operation is displayed at the top of the Hierarchy rules table. The notification contains a link that you can click to see a table containing the
On the hierarchy rules detail page, click Simulate log details.in the appropriate row to simulate the execution of a hierarchy rule. A notification regarding this operation is displayed at the top of the Hierarchy rules table. The notification contains a link that you can click to see a table containing the
The following video (2:48) describes how to restore a tree that is loaded by an ETL in workspace, after the tree is modified due to manual actions or reconciliation.
You can restore the object relationship for the hierarchy rule to a restore date that you specify. To do this, perform the following steps:
By doing this, the analyses, models, and reports using historical information, use the current object relationship that is valid from the restore date.
You can view the log details for the hierarchy rule by clicking Show log , in the corresponding row on the hierarchy rules detail page. A table containing log details like Timestamp, Reference date, Type, and Message is displayed, as shown in the following figure:
Example of execution log details page
In the table containing the log details, you can perform the following actions:
The following table lists the readily available hierarchies available in TrueSight Capacity Optimization.
Hierarchy template name
Aggregate Business Driver by Domain
Generates an aggregate business driver for the domain.
|CO Agent derived metrics||This is an automatic template (Gateway Server ETL).|
|CO Aggregated Workloads||This is an automatic template (Gateway Server ETL).|
|Cloud hierarchy||This is an automatic template (Cloud Lifecycle Management ETL).|
|Derived Entities||This template is used while adding a derived system or a derived business driver, managed in the Workspace section.|
Facility Solution - CRAC Power from Compressors
Generates CRAC Power Utilization from Compressors Power Utilization.
Facility Solution - Line from Rack
Generates Line Power Utilization from rack data.
Facility Solution - Rack from PDU
Generates Rack Power Utilization from PDU data.
Facility Solution - Room from UPS/AC
Generates Room Power Metrics from UPS and AC data
Facility Solution - Room from Line
Generates Room Environmental Metrics from Line data.
Facility Solution - UPS Power from Phases
Generates UPS Power Utilization from Phases.
Guest Machines - AIX
Generates virtual machines hierarchies based on data collected from pSeries system host.
Guest Machines - HP Integrity
Generates virtual machines hierarchies based on data collected from HP-UX system host.
Hardware Model Aggregation
Aggregates all machines of the same hardware model.
Handles the explicit relation dataset (OBJREL). Generally it’s automatically configured.
|OpenStack Cloud hierarchy||Aggregates the data for OpenStack cloud entities.|
Operating System - Environment Machines
Aggregates all machines of the same operating system and environment.
Physical Host Aggregation
Aggregates of all partitions of the same physical host.
|RHEV aggregation rule for partial collection||Aggregates of RHEV partial collections.|
Generates Solaris system hierarchies based on collected data.
Generates Solaris Zone hierarchies based on collected data.
Typical Business Driver by Domain
Generates a Business Driver equivalent for the domain.
Typical Physical Machine for Application Layer
Creates a Physical Machine equivalent for each Application Layer.
|Typical Virtual Machine||For each Virtual Host/Virtual Cluster, creates an additional Virtual Machine that represents the average utilization of resource due to their running Virtual Machines.|
|Typical Virtual Machine for Application Layer||Creates a Guest Machine equivalent for each Application Layer.|
|VMware Aggregation||Aggregates the data for top level VMware entities like resource pool and cluster.|
|vCloud Aggregation||Aggregates the data for top level vCloud entities like vCloud organizations and vCloud applications.|