Splunk satisfied your company’s curiosity when it came to understanding what could be extracted from the numerous (un)structured log files that reside across a given network, application, database or security infrastructure. HP’s BSM is designed for pulling together a horizontal and vertical perspective of the application service transactions and related underpinning app/infrastructure architecture. With Splunk forwarders presently being proliferated across the enterprise it’s time to bind the relevant topology, metrics and/or events from Splunk into HP’s Manager of Manager (OMi) while applying the appropriate SBEC and TBEC correlations across the composite and available datasets to provide a view into the Services of your organization separating the cause from its apparent symptoms.
Using Melillo’s BSM XtractorTM for Splunk topological data (CIs) can be extracted to enrich OMi service modeling where instrumentation is blind or missing to best accentuate the interrelationships of services across the data center. Events can also be filtered and correlated with its associated topology to assist in pinpointing issues while critical metrics can be extracted from Splunk to assist in evaluating the tiers in your services as they relate to the models that bind them together.
Suggested for you are based on app category, product compatibility, popularity, rating and newness. Some apps may not show based on entitlements. Learn more about entitlements.
The attached document outlines how to synthesize events from your current Splunk implemenation using the 9.24 or prior HP BSMC with our custom Python script. Version 10 of this events only script will be available in Q4 of 2015.
Please upgrade to one of the following broswers: Internet Explorer 11 (or greater) or the latest version of Chrome or Firefox