IT Operations Management (ITOM)

Content development and extensibility in HP Service Health Reporter

Content development and extensibility in HP Service Health Reporter


It is common for IT organizations to use multiple products from multiple vendors and cross-domain reporting on performance of the infrastructure elements is often a necessity.

Keep reading to find out how you can easily develop content to report on the IT Performance Management Data in this type of an environment.

Customers use multiple products offered by various vendors to monitor and manage their IT infrastructure and services. Now you have the option to have a consolidated reporting under one convenient canopy. The HP Service Health Reporter (SHR) product which is a part of Business Service Management (BSM 9.x) portfolio offers a singular platform for data warehousing that caters to the reporting and analysis of IT Performance Management data.  Decision support systems based on centralized BI are used for intelligent decision making utilizing the past performance of business services. The out-of-the-box content packs in SHR are designed to provide the same information.

When you consider the heterogeneous performance monitoring environments, a content pack for performance reporting needs to:

  • Anticipate data pertaining to the same domain from multiple management sources and
  • Support integrations across source product versions which differ substantially in terms of structure and content. 

This data needs to be made available for a myriad set of use cases for analysis and reporting and it needs to be available for customizations as per end user requirements. There is an inherent complexity in designing content packs as solutions that address the afore-mentioned use cases.

The content pack design and its development process in SHR are streamlined by bringing in a layered architecture amongst content packs. This provides flexibility in integrating with additional data sources (different products/vendors) and also in creating customized application content in various deployment scenarios.

The layered/multi-tiered content pack structure is well-suited for extensibility and customizations.

These are the 3 layers of content:



Core Domain content packs:

                Domain specific content packs which define the data model for a particular domain. They drive the content schema creation and workflow.

ETL (Extract, Transform, and Load) content packs:

                Source specific; targeted for the ETL layer designed to extract data from the various sources, cleanse and transform the data.

Application or Report content packs:

Application content packs define specific content addressed towards a particular reporting use case. They also expose the business view (logical data model). Application content packs in SHR can leverage the pre-defined logical models defined in the core content packs. In addition, they have the flexibility to extend the data models defined in one or more core content packs on which they depend on. This application layer is generally materialized using a reporting/BI tool.


HP Service Health Reporter offers a tool for Content Development (CDE) which is available from v9.20 of the product. The tool has provisions both for building new content as well as on extending new content.

We have a six-part video series available which gives a quick overview of SHR Content Development.


This Content Dev Video Series includes...








Part 1: Content Dev Overview









Part 2: Domain Content De-mystified









Part 3: Data Roll-ups: The power of dimensional analysis








Part 4: ETL – Potpourri of data integrations







Part 5: Report Development








Part 6: Creating My First SHR Report




This approach for developing content is extensible, thereby providing flexibility for: 

    • Creation of BI artifacts and Database vendor agnostic Core Domain model
    • Integrating multiple data sources with a pre-defined domain specific data mart (content pack) and this can be done incrementally as well.
    • Building multiple application content packs (that could be cross-domain) pertaining to various BI use cases incrementally
    • Integrating multi-vendor based sources whilst preserving the core domain content packs
    • The layered architecture provides ease of development and the provision to build further on top of existing content. 



  • operations bridge
0 Kudos
About the Author


Valued Contributor.

Hi Vineetha , 


Is there any content pack develope going on in HP SHR for QA and Traffic reports ?