Operations Bridge: OM-to-OpsBridge evolution enhancements

by in IT Operations Management

In an earlier blog post introducing the highlights of the Operations Bridge 2018.11 release, we have already announced that we’re making continuous progress on our journey to deliver a flawless Operations Manager (OM) to Micro Focus Operations Bridge evolution experience. This blog offers more details on the newly implemented evolution enhancements, in particular:

  • Cluster-aware monitoring. This feature was used by many Operations Manager users in the past to simplify monitoring of clustered applications.
  • Enhanced node configuration report. The report now reflects how exactly a configuration item is monitored – down to the parameter values which play an important role in Operations Bridge Manger (OBM), formerly OMi.
  • Improved Monitored Nodes User Interface (UI). The UI is now able to handle up to 20,000 nodes (this is comparable to the Operations Manager scalability).
  • A pattern-matching test tool for the HTML Log File Entry Policy Editor. This enhancement was requested by the Operations Manager for Windows users to facilitate finding patterns during the policy development.

Out-of-the-box cluster-aware monitoring with the OBM Management Pack for Microsoft SQL Server

The Operations Bridge 2018.11 release provides significant improvements in the area of monitoring highly-available clustered applications by introducing out-of-the-box cluster-aware monitoring for Microsoft SQL Server.

The OBM Management Pack for MS SQL Server discovers the clustered Microsoft SQL Server and creates a corresponding cluster model in the RTSM, thus making OBM aware of the cluster environment. The below diagram shows the RTSM model discovered out of the box by the Management Pack:

RTSM model.pngAs you can see, the relation of the Microsoft SQL Server to the physical node no longer exists; instead, there is a relation to the virtual node (or the HARG) resulting in discovery of the HARG.

Note: A high-availability resource group (HARG) is a collection of resources that are available on one of the physical nodes of the cluster and can be switched to another cluster node as a single entity.

Virtual nodes are presented in the RTSM as CIs of the cluster_resource_group type. A virtual node CI is assigned the host name and the IP address belonging to its HARG. The central attribute of a virtual node CI is its HARG name.

Related monitoring aspects are assigned in OBM to the Microsoft SQL Server CI directly. The person assigning an aspect does not have to know if the SQL Server is clustered or not. OBM then deploys monitoring to the corresponding physical nodes. The policies are enabled on the active node (the node hosting the HARG) and are disabled on passive nodes. If a failure occurs, the application is moved over to the other node in the cluster. It is important that the monitoring switches immediately as well, in order to avoid monitoring downtime. In such a case, the Operations Agent automatically determines which node is now hosting the application/HARG and enables monitoring on it. As this functionality is now available out of the box, it takes little effort to configure and use it! In fact, all you need to do is to assign monitoring to the Microsoft SQL Server CI you want to monitor; the rest is taken care of by Operations Bridge.

Note: Another option is to assign monitoring aspects to a virtual node (similar to the functionality available with Operations Manager). This is a possible but not recommended scenario, as we encourage our customers to take advantage of the CI-based (topology-centric) approach as opposed to the node-based approach practiced with OM. To learn about the benefits of the CI-centric approach and get information on how to establish the RTSM topology, please see this topic in the Operations Bridge Help Center.

For detailed information, please see a separate blog article (will be available soon) that discusses general concepts and challenges of the cluster-aware monitoring and provides the details on how the cluster-aware monitoring is implemented in Operations Bridge.

Improved Node Configuration Report

Previously, the node configuration report had a few gaps in showing parameter values. With Operations Bridge 2018.11, these gaps have been addressed by implementing the improvement enabling you to verify the deployment status of direct, indirect and proxy assignments with the parameter values:

  • The CLI report has been enhanced to show parameter issues between the desired state in OBM and the deployed state on the node
  • The new web service is included in OBM, which you can use to generate custom reports with parameter issues

Note: This enhancements has been implemented as part of moving away from node-centric deployment to CI-centric deployment and parameterization functionality in OBM.

See this blog post describing the feature for comparing the agent-based policy configuration with the desired state on the OBM server, and the concepts behind.

Improved Monitored Nodes Admin UI Scalability

With Operations Bridge 2018.11, you can view the large list of nodes – up to 20 000 – in the Monitored Nodes UI. This is especially useful for those of you who have a large number of nodes to be monitored (in earlier releases, it was necessary to create multiple filters to view big numbers of nodes).

The maximum number of nodes displayed in the Monitored Nodes UI can be configured in Infrastructure settings. The default is 20 000 nodes. As an additional improvement, we should mention the "lazy" loading of node details to accommodate fast loading of a large list of the nodes.

Pattern-Matching Test Tool for HTML Log File Entry Policy Editor

Another step towards a plugin-free UI and better user experience is introducing a pattern-matching test tool for the HTML Log File Entry Policy Editor.

This feature brings the benefit of faster policy development through the use of the pattern-matching tool which simplifies finding the right patterns during the policy development. (A similar pattern matching test was also provided with Operations Manager for Windows.) The tool is designed to support you in developing the patterns used in the policy rules and follows the new Micro Focus style and usability concepts.

In the screenshot below, you can see how the tool allows upload of log files and typing of log lines to check. It then shows which pattern of which condition matched which line:

PM test tool2.png


We encourage you to try out our new features and enhancements! For further information on our offerings, visit the Operations Bridge product page, explore our documentation resources and check out our videos and blogs.

If you have feedback or suggestions, don’t hesitate to comment on this article.

Explore full capabilities of Operations Bridge by taking a look at our Operations Bridge Manager, Operations Bridge Analytics, Operations Bridge Reporter, Operations Connector (OpsCx), Business Value Dashboard (BVD) and Operations Orchestration (OO) documentation!


To get more information on this release and how customers are using Operations Bridge, we are happy to announce the following events:

Read all our news at the Operations Bridge blog.


Explore all the capabilities of the Operations Bridge and technology integrations by visiting these sites:


Operations Bridge
  • In the Monitored Nodes UI, you can only view a limited number of nodes (based on your screen/font size) – “lazy loading” means that only this amount of node details is loaded. Once you scroll through the node list, it is loaded dynamically – the further down you scroll, the more and more data is being displayed. This allows to handle very large number of nodes as it avoids loading all the node information at once. It’s also worth mentioning that the Search feature searches through all the nodes, not only through the ones that are currently displayed in the UI.
  • When can we expect cluster aware monitoring for Oracle MP?

  • "The maximum number of nodes displayed in the Monitored Nodes UI can be configured in Infrastructure settings. The default is 20 000 nodes. As an additional improvement, we should mention the "lazy" loading of node details to accommodate fast loading of a large list of the nodes."

     What you meant by that "lazy" loading ? I cant find any option for that.