Some time ago, we had a blog post on the new avenues made possible via HP Service Health Reporter (SHR’s)northbound interface.
Let’s now take a look at what’s up on the southern front …
HP Service Health Reporter (SHR) offers cross-domain IT reporting on enterprise IT performance data. It is powered by a model-driven architecture… which is leveraged by thethird-party domain integration possibilities via BSM Connectors described in this blog article. These indeed are added testimony to the fact that a generic domain data model enables cross-domain, data-source-agnostic reporting in SHR.
In practice, we come across heterogeneous deployment scenarios wherein organizations potentially have multiple domain managers/technologies in place for monitoring IT environments. However, a single consolidated reporting interface is preferred.
In line with the philosophy of the comprehensive Operations Bridge solution, this is now made possible with SHR reporting as well… The intent of this blog post is to offer an overview of how such solutions can be enabled via BSM Connector (BSMC) 10.x integrations in SHR.
Third-party Data integrations via BSM Connectors
BSM Connector integrations serve as an intermediary between heterogeneous domain managers who are transferring event, topology and metric data from third-party domain managers to the Operations Bridge.
The integration channel can be viewed as a pipeline …
As you see in the flow diagram above, BSMC integrations collect different types of data. These are transferred and stored in the appropriate Operations Bridge components:
Event data is persisted in the OMi Event database
Topology data is directed to OMi RtSM (Run time Service Model)
Metric data is stored locally on the BSM Connector server inside the Operations Agent performance store.
Connectors therefore bring in the key benefits of integrating IT Management data into the Operations Bridge, making use of BSMC’s data retrieval facilities – do check out the BSM Connector third-party domain manager integrations readily available on HP Live Network.
Enabling third-party integrations for reporting via BSMC
Now let us take a look at some of the details surrounding how data thus channeled in, can be leveraged for reporting in SHR.
Events: Event data that is persisted in OMi Event store is automatically reported on by the SHR out-of-the-box content pack on OMi Events.
Metrics: There are two scenarios that one could think of in this context:
1. New SHR Content creation
This involves the development of new domain/reports content components in SHR apart from those offered out-of-the-box. To get started on this, see the SHR Content Development Guide.
For the ETL integration that is specific to integrating with BSMC, read on through the next point.
2. New ETL extension for an existing Domain content
Domain reporting content is already available in SHR [see SHR Content Catalog for reference], in which case an ETL integration from the Connector metric store is all that needs to be developed in SHR.
Here is a list of steps involved in developing this ETL component:
Create Topology View in OMi10 containing monitored instances/BSMC server instance
Create ETL Content using CDE: Author the RtSM and Agent collection policies and stage rules [and also required transformation and reconciliation rules].
Build the ETL Content: Create the manifest xml for SHR ETL content; compile the ETL content using CDE.
Deploy the generated ETL package on a SHR system.
Details on these steps and added tips for BSM Connector integrations and detailed illustrations [taking Nagios integration as an example] are available in the SHR: Integrating with BSM Connectors guide available on the Community.
The newly added topology via BSMC can be filtered via a custom tql or view, which could then be leveraged in SHR topology collection using standard content development steps.
The afore-mentioned guide also covers topology data import.
Yet another illustration on bringing in additional topology information is available in the RtSM Extended Content that is offered on the Community.
Thus, SHR out-of-the-box reports can be leveraged for data fetched via the BSMC ETL integrations [for example: reporting on Microsoft SCOM data via SHR System Management/Active Directory/ExchangeServer content]. For additional domain areas, new reporting content can be built out as well.