Moviri - HP Reporter Extractor

"Moviri Integrator for BMC Helix Continuous Optimization – HP Reporter" allows collecting information from HP Reporter tool and it is able to extract and summarize resources performance data, configuration data and relationships between infrastructure entities.

All data collected can be analyzed using BMC Helix Continuous Optimization tool, in order to:

• Analyze resources usage
• Perform trend analysis and forecast analysis
• Gain at-a-glance control over IT infrastructure capacity with BMC Helix Continuous Optimization Virtual Farm Views
• Perform capacity optimization and planning

The connector supports configuration parameters that allow systems and metric collection filtering, historical recovery, limiting data volume processed in a single run, specifying data resolution and many other settings.
The documentation is targeted at BMC Helix Continuous Optimization administrators, in charge of configuring and monitoring the integration between BMC Helix Continuous Optimization and HP Reporter.

Requirements

Supported versions of data source software

• HP Reporter 3.80 Eng

• HP Reporter 3.90 Eng

• HP Reporter 4.00 Eng

In order to collect data and relationships between IBM LPARs and Frames, the following product needs to be installed on monitored LPARs: HP Operations Smart Plug-in for Virtualization Infrastructure for HP Operations Manager

Supported configurations of data source software

HP Reporter can support various DBMSs for storing data; "Moviri - HP Reporter Extractor" supports the following:

• Oracle Database 11g

• Microsoft SQL Server 2008 R2, 2012

Datasource Check and Configuration

Preparing to connect to the data source software

As a first step, please ensure that the correct version of HP Reporter is installed. You can perform this check from the "About Reporter" section of the Console:

Please also ensure that the DBMS version is compliant with the aforementioned list.
By default, HP Reporter is configured to permanently store in its database the data that is collected from agents only for a set of predefined metric lists:

• APPLICATION
• GLOBAL
• SYSDOWNTIME
• TRANSACTIONS
• UPTIME

These metric lists include only a subset of the metrics that can be imported by "Moviri Integrator for BMC Helix Continuous Optimization - HP Reporter". Please refer to HP Reporter official documentation for additional information.
In order to properly set up the HP Reporter data source for integration in CO, the following set of metric lists should be created (names are suggested):

• CPIT_APPLICATION (metric class "Application")
• CPIT_DISK (metric class "Disk")
• CPIT_FILESYSTEM (metric class "Filesystem")
• CPIT_GLOBAL (metric class "Global")
• CPIT_LOGICAL (metric class "Logical")
• CPIT_NETWORK (metric class "Netif")

And only for AIX Logic systems, two metric classes enabled by deploying on the monitored host HP Operations Smart Plug-in for Virtualization Infrastructure for HP Operations Manager

• CPIT_FRAME_CONF (metric class "Frame conf")
• CPIT_LPAR_CONF (metric class "Lpar conf")

Access to the HP Reporter console is needed to perform the above operations.
In HP Reporter, you can either create a new metric list as a copy of an existing one, or from scratch. Please refer to Section 9 for the full range of CO-mapped metrics.
After the creation of the metric lists, they need to be added to Discovered Systems > Metric Lists (by drag and drop); eventually Run All button must be pushed in order to build proper tables inside Reporter database.
The BMC Helix Continuous Optimization ETL should access the data source by means of a database user having read-only access rights on the schema (and therefore, the tables) containing the data to be collected. The database user should be created directly on the DBMS (by the Database Administrator), and not from the HP Reporter Console.
The procedure, according to HP Reporter manual, should proceed as lsited below for each new metric list:

1. Add a new Metric List
   

   

   
   

2. Define properties for the newly created metric list, as depicted in the following figure:
   1. Name.
   2. Source Class.
   3. Data resolution.
   4. Data retention.
   5. Data sources.
   Then, add metrics from Data sources according to the list of suggested metrics (see table at the end of current section).
   
   

   
   

3. Activate data gathering for the defined metrics list on all available systems

 

This is a summary of the configuration described in this section. The data resolution setting can be customized according to specific reporting needs, in which case one ETL task for each data resolution is to be set up.

 

For the full range of metrics that can be added to the above metric lists please refer to section "Configuration and Performance/Business Metrics Mapping", subsection "Configuration Metrics".

Connector configuration

Connector configuration attributes

There are three sections (tabs) in the ETL run configuration page where the behavior of "Moviri - HP Reporter Extractor" can be specified:

• HP Reporter - Data selection
• HP Reporter - Settings
• Connection parameters

HP Reporter - Data selection

 

 

HP Reporter - Settings

 

Historical data extraction

In order to perform a historical recovery of data, please use the default, "lastcounter"-based mechanism of CO, i.e. change the current value of the desired lastcounter.
If the ETL task is newly created and has no lastcounter defined, the "default lastcounter" can be used

Supported Platforms

For all metrics imported by the ETL and described in this section, the following apply:

• Supported platforms: Standalone OS Instance, AIX Power VM Hosts and LPARs, Solaris Containers
• Supported BMC Helix Continuous Optimization Entity Type: System (Generic), Solaris Zone, Solaris Virtual Host, AIX LPAR, AIX SPLPAR, AIX Virtual Host

 

Troubleshooting

 Missing data can represent a frequent problem; in this case a WARNING status would be associated to the ETL task. This can be due to a number of scenarios, among which:

• The data is not present on the HP Reporter data source. In order to verify this, it is suggested to run the HP Reporter reports against the considered time range.
  
  

Figure 23: Generation of HP Reporter Reports

• The data is available on HP Reporter, but the ETL is not able to extract it. This could be the case when the ETL task is executed before new data (since the last collection) is available on the data source. The last counter, which contains the highest time stamp collected in the previous run for that table (and is used as a time threshold for ignoring old data), is higher than the data to extract timestamp.

The lack of extracted data (see the following log example) indicates that new data might not be available in HP Reporter. In this case, the previous condition applies and the recommendation is to run the ETL at a later date.

 

 
Moreover, it is strongly recommended to avoid creating an Integration Studio ETL module with the same name as this ETL (HPReporterME), which would likely cause unexpected behavior.

Configuration and Performance Metrics Mapping

Configuration Metrics

The following configuration metrics are imported into CO:

Metrics with * were previously custom, remapped as standard after v 3.4.00

Performance Metrics

The ETL connects to the Reporter Warehouse instance and extracts data for metrics belonging to specific HP Reporter metrics’ classes. These classes of performance  metrics are populated by HP agents and refer to:

• Generic OS instances
• Solaris Zones
• Solaris Virtual Host
• AIX LPAR
• AIX Virtual Host

The full list of known classes and metrics, and the mapping between HP Reporter metrics and BMC Helix Continuous Optimization metrics is reported in the listing below.

Inside all metric lists created in HP Reporter, it is important to include the INTERVAL and GLB_INTERVAL columns, wherever applicable.

Lookup Fields

Moviri Integrator for BMC Helix Continuous Optimization connector uses standard BMC Helix Continuous Optimization ETL lookup mechanism. One single entry is used as entity identifier: Lookup field = “DEFAULT”.

Here below a lookup tables as example:

Object Relationships

The ETL assigns all imported entities under a domain (which can be configured by the user).

• Imported Relationship Types:
  • “Domain to system” APP – SYS [identified by its data source name, DS_SYSNM], where APP is the domain of choice (as selected in the “Object Relationships” tab in the Run Configuration wizard)
  • “System to System” SYS [VH] – SYS [GM],
    • Solaris zone are connected to their container host (see Figure 26)
    • AIX LPAR are connected to their frame host

A hierarchy rule associated to the ETL is automatically created by BMC Helix Continuous Optimization to process the Object-Relationship data.