Connecting with Metric Manager
To integrate Metric Manager (formerly IBM® Operations Analytics Predictive Insights) with IBM Cloud Pak for AIOps , first ensure that you implement the prerequisites, and then change the rules file in Metric Manager.
Note: IBM Cloud Pak for AIOps comes with built-in metric capabilities. Connect with Metric Manager only if these capabilities are insufficient to your needs.
Prerequisites
To allow the forwarding of event data from Metric Manager to IBM Cloud Pak for AIOps , and the integration of both, do the following:
-
Event forwarding from Metric Manager to IBM Cloud Pak for AIOps is done by forwarding from the on-premises objectserver to IBM Cloud Pak for AIOps by using a uni-directional gateway. To set up this gateway, follow the instructions described here.
-
For Metric Manager 1.3.6 integration with IBM Cloud Pak for AIOps , apply InterimFix005 available here.
Procedure
Change the rules file in Metric Manager. Make the following changes to the rules file (located here: $PI_HOME/probe/omnibus/probes/linux2x86/stdin-tasp.rules) in Metric Manager.
Note: Ensure you backup the rules file before you edit the file.
-
In the file, locate the following two lines:
#@Identifier = @Node + " " + @AlertKey + " " + @AlertGroup + " " + @Type + " " + @Agent + " " + @Manager @Identifier = $Identifier
Remove the '#' from the first line and add it to the start of the second, so that it changes to the following:
@Identifier = @Node + " " + @AlertKey + " " + @AlertGroup + " " + @Type + " " + @Agent + " " + @Manager #@Identifier = $Identifier
-
Add the following before the last closing bracket "
}
", replacing "PI_UI_HOST.example.com=
" with the fully qualified domain name of the Metric Manager UI host:@URL = "https://PI_UI_HOST.example.com:9998/predictiveinsights/jsp/wlp/wlpAnomalyView.jsp?anomalyKey=" + $TASPIdentifier update(@URL)
-
Add either of the following just after the last closing bracket "
}
":-
IBM Cloud Pak for AIOps
#For integration with IBM Cloud Pak for AIOps : if (regmatch($Class, "89350") || regmatch($Class, "89360")) { @AlertGroup = "ANOMALY:" + @TASPAnomalousMetricGroups + ":" + @TASPAnomalousMetrics update(@AlertGroup) } ## Note: Do not forward these consolidated events from Metric Manager, as the downstream system will do this grouping: if (regmatch($TASPIdentifier, "Node") || regmatch($TASPIdentifier, "RelatedEvents") || regmatch($TASPIdentifier, "Incident")) { discard }
-
IBM Cloud Pak for AIOps Event Manager
#For integration with IBM Cloud Pak for AIOps Event Manager if (regmatch($Class, "89350") || regmatch($Class, "89360")) { @AlertGroup = "ANOMALY:" + @TASPAnomalousMetricGroups + ":" + @TASPAnomalousMetrics update(@AlertGroup) } $Identifier = regreplace($Identifier, "(_\d{13}$)", "" ) @Identifier = $Identifier update(@Identifier) ## Note: Do not forward these consolidated events from Metric Manager, as the downstream system will do this grouping: if (regmatch($TASPIdentifier, "Node") || regmatch($TASPIdentifier, "RelatedEvents") || regmatch($TASPIdentifier, "Incident")) { discard }
-
-
To start the gateway, run the following:
cd /opt/IBM/tivoli/netcool/omnibus/bin nohup ./nco_g_objserv_uni -name NCO_GATE -propsfile /opt/IBM/tivoli/netcool/omnibus/gates/aiops/aiops.props &