IT Operations Management (ITOM)

HP Service Health Reporter: Performance Insight Migration Part 1 – An overview of the migration approach and scenarios

HP Service Health Reporter: Performance Insight Migration Part 1 – An overview of the migration approach and scenarios


HP Service Health Reporter (SHR) is the new consolidated, model-driven, cross domain enterprise reporting and data warehousing platform for HP Software. 


SHR provides a very rich set of out of the box reports for HP Software’s Operations bridge environment including systems, virtualization, infrastructure applications like Oracle, MS SQL Server, J2EE application servers, event management, application management domains. On top of providing consolidated reporting, SHR also provides reporting based on models, views and groups which are defined in BSM runtime Service model (RTSM) or OM.


The SHR framework is also an excellent platform for developing new content and integrates with additional domains not covered by SHR out of the box. SHR is an enterprise level reporting product with the capability to scale to large environments and supports enterprise reporting features like high availability, shifts, downtime, advanced filtering and parameterized report generation, report scheduling and delivery via email. SHR embeds the popular Business Intelligence tool Business Objects (BObj) from SAP for report visualization and development on top of HP’s own performance management oriented data warehouse environment and collection framework.  See the sales portal for regular updates to SHR marketing assets.


HP’s previous reporting product HP Performance Insight (PI) also has a large customer base and it also provides consolidated reporting from multiple domains. But primarily, the focus of PI was around systems and network management domains. It is HP’s goal to migrate the existing PI customers to SHR because SHR is HP’s flagship reporting product going forward and SHR has been designed carefully to cover most of the reporting requirements and contents of PI. Since network management is also a major part of PI product functionality, HP software provides market leading NNM iSPI for Performance reporting product to cover the network performance reporting functionality of PI. So, the two products, SHR and NNM iSPI for performance together provide a much broader set of functionality coverage for systems, application and network performance reporting which can be a very attractive solution for PI customers to migrate to.


PI Migration Summary


PI customers are primary divided into five general categories:

  1. System Management Reporting: Customers focused on System Management area and customers who are using Operations Management product suites and HP Operations/Performance agents for collecting data and reporting on that data. These customers usually also have the Operations Management SPIs.
  2. Network Management and Network Device Management Reporting: Customers who use PI to collect data from their Network Infrastructure domains and used out of the box and customized PI reporting for this Network Domain areas. The majority of the Network domain customers are using PI IR (Interface Reporting) and DR (Device Reporting) report packs of PI but there are customers who are using other PI Network report packs as well such as MPLS, QoS and others.
  3. System and Network Combined/Infrastructure Reporting: There are some customers who are using PI for both System and Network Management reporting needs. Although System and Network Management in IT is getting more and more specialized in each of their own domains, but from reporting perspective many customers and IT Managers are taking a holistic view and use the same data warehouse, reporting and forecasting tool such as PI.
  4. Telco Customers: PI is an open product and has good capabilities for collecting SNMP device data. This enables many Telco customers to use custom built solutions for their Telco environment management with PI. Many of these customers also used standard PI for their non-Telco infrastructure reporting along with their Telco devices.
  5. Other Customers: Since PI was a do-it-all type of a tool, there are few customers who have used PI for some custom reporting solutions for very specific devices. Again these customers used PI in a completely non-standard ways without any out of the box reports.


With SHR 9.30, we primarily focus on Category 1, 2 and 3 to migrate to SHR. This covers bulk of customers using PI (95%).

SHR provides excellent coverage for system management domains including systems and SPI based infrastructure application management.  The traditional Operations Management without the presence of run time service model (RTSM) is also fully supported by SHR. So, PI customers can easily migrate from PI to SHR if they are using PI for reporting on these domains (system management and SPIs with traditional Operations Management).  SHR also provides an upgrade path to customers who are planning to move up from traditional Operations Management to Service & Operations Bridge oriented management.

A large set of PI customers are focused around network management domain based collection monitoring and reporting. SHR does not provide coverage for data collection from network devices. For network devices and different network monitoring domains, the collection is covered by HP’s market leading NNM product suites and collections. The network performance data warehousing and reporting is covered by NNM iSPI reporting product suites.


SHR however, provides capabilities to integrate with NNM iSPI data for consolidated reporting and customization of reports. Out of the box, SHR brings in network devices and interface data and provides summary reports with consolidated network and system management reporting. The detailed network node and interface reports are not covered by SHR as they already exist in NNM iSPI for Performance. The network device and interface data (hourly grain) is available in SHR and published in SHR’s Business Objects universe for easy customizations.  


HP plans to provide use case driven migration for PI customers depending on the way the customers are using PI:

  1. System and Application Infrastructure (SPI) oriented performance reporting: Customers get migrated to SHR and SHR provides coverage for PI use cases and reports.
  2. Network performance reporting: Customers get migrated to NNM iSPI for Performance reporting suite and they are also entitled to use SHR if they desire. In this case SHR can be used for analytical/consolidated reporting to combine network domain data with others/use custom data and pursue customizations in reporting.
  3.  System & Network Infrastructure performance reporting: In this case customers are using PI for both Systems and Network Management reporting. In this case, the migration will be addressed with combined SHR and NNM iSPI for Performance based solution. SHR can be used for system and application reporting as well as consolidated and customized reporting. NNM iSPI for Performance is used for network infrastructure performance reporting. If the customer wants customized reports on either network or system management domain, they can use SHR as the common customized reporting platform because SHR provides integration with NNM iSPI for Performance data. In SHR 9.2 and 9.3 releases, SHR imports NNM iSPI’s network device and interface data and provides executive and summarized reports on these data. Also all network device and interface data are published via SHR semantic layer for easy creation of any customized reports on top of this network data.


In all of the above cases, different customers use different Report packs of PI to cover their Management Domains. SHR out of the box content has good coverage of System Management, Virtualization and Operations Management SPI content. The NNM iSPI content packs also provides good and super set coverage of Network domains but additional Report packs of iSPI may needs to be deployed along with base iSPI to fully cover the PI Network domains.


                         Please refer to further blog posts on this site regarding additional details on all the above scenarios. .. 

  • operations bridge
About the Author