OpsBridge has good event correlation facilities and root-cause identification algorithms. This can reduce the number of alerts that an operator sees, potentially improving operator efficiency and reducing the "cost-per-alert".

To achieve this though OpsBridge depends on accurate topology mapping, i.e. it needs to understand the dynamic relationships between items being monitored. Maintaining this can demand additional software.

As owners of the Vertica database, MicroFocus can exploit this technology to improve the handling of the vast amounts of monitoring data that its enterprise customers generate.

We have a bunch of critical servers and applications. We are able to monitor using this product to create a dashboard and have automatic alerts to notify the responsible team.

We’re now transforming three teams into one, and others will follow in the coming years.

It decreases our time to fix problems and it takes less time to find the root cause. A lot of the process is done with the Artificial Intelligence (AI) that is built into the system. It helps us nail down the root cause faster. It has also reduced our costs.

The biggest strength of the Operations Bridge is the consolidation of events from various sources. For one customer, we were able to consolidate events from more than 25 sources, most via Traps using a BSM Connector. Once the Head of IT Operations saw the value, then the expectation was that all the other siloed departments would work together to send the events to a central console.

You don't waste time launching multiple applications. You can actually have information right there in front of you. Again, it quickens the mean time to recover.

It has greatly reduced the number and duration of outages as support teams are notified immediately when something goes wrong or even before something breaks. The integration with the ticketing tool makes sure that there is a record for every issue.

It helps to integrate and consolidate various products, such as Operation Manager, Operations Bridge, OMi, Operations Bridge Reporter, Operations Connector, Network Node Manager, Universal Discovery, ServiceNow, and NOC, which use one single screen to monitor the entire infrastructure. SBEC (Stream-Based Event Correlation) event correlation has helped consolidate events into one event helping to reduce events visible to operators letting them act and find root causes more quickly. It has helped to handle message storm situations. Earlier NOC were using different screens to monitor different environments. Now, they have to look at single screen as other products are well-integrated with OMi. 

At the moment, we're still building the system, so I can't say.

It's our monitor of managers. It's our monitoring tool and it looks after all our servers.

Actually, we're going to see measurable results maybe next year. We haven't had it in wide production use for that long yet, so I can't mention percentages, really. But so far, the experience has been that it enables automation from sources that usually don't support automation.

Also, it's just a very nice place to do some basic correlation and things like that. We've been using fairly old technology user interface-wise before this, so it's a nice upgrade for operators to operate in.

The transparency shows us where we still have to add things, monitor things that we don't have under our control yet.

For its fundamental proposition and as far as the way it works, it works well. It's a strong product; it has a wide capability - especially if you integrate it with more application performance-related solutions - and if you have infrastructure scanning, those two work together well. The data model and the data flow is pretty good, so overall it's a product that definitely adds value in a complex organization; complex in terms of infrastructure and application infrastructure. It's definitely a good product.

It has improved the working of our company, especially the working of our operation team. They have much more view on the servers and what is happening with them. They know when to act and on what to act. The alarms are very clear. There is only one central database for all the alarms; before we had to look on different systems.

It has not only the servers but also our network is in there. It's an all-in-one dashboard for our operations team so that is very helpful.

When we first transformed from being on premises to going significantly into the cloud, we had to go ahead and change a lot of our enterprise architecture and landscape. We needed to be networking very differently and to be leveraging virtual machines on the cloud very differently and in a cost-optimal way. This clearly meant that our internal IT had to operate very differently from what they were used to in the past. We needed to get them to change themselves and work differently so they could provide these kinds of services. IT needed to be able to give me the kind of resiliency, simplification, standardization, agility and the promise of the cloud with optimal cost. This was something which was important, and that's what it did to transform our IT.

It identifies parse issues pretty quickly. Instead of logging multiple tickets, we actually deduplicate those and just create one ticket, which makes our operations a lot easier to manage during the incident.

I'm not using it now, but when I was, it was the capability of auto fixing issues that could be customized per device, OS, or application. That seemed to make people the most excited.

We have a central screen that alerts us to problems from all parts of the business. This enables our operations team to have visibility of all issues and deal with them or call out as required.

It keeps our IT systems functioning, which for our company is absolutely essential.

It optimizes their operations efficiency, and makes people more focused on the issue at hand instead of trying to figure out what's going on. It gives them an up-to-date status. If there's an issue in the IT system - whether it's a server, network, application, or resource issue – the product emphasizes it and gives you tools to troubleshoot and resolve it.

It gives businesses the ability to monitor their services with dashboards that show whether those services are working properly. For example, if the business is a bank and its customers can't take money from an ATM, the bank ultimately loses a lot of money. They need to be able to constantly check their the health and performance of this important business service.

It helps me on a day-to-day basis. We used to have our services monitored by two isolated islands. One island was from the IT perspective, with servers and operating systems. The other island looked at the service from a resource perspective, with routers, switches, and an aggregation layer.

HPE helped us aggregate, and we now have all these layers in one layer. We're now looking at the service from the core of it, not from a resource perspective or from an IT, servers-based perspective.

It gives us the ability to monitor the entire infrastructure proactively and reactively. We can build incident event management and problem management processes in case of a problem so that an event is registered. We can then change the event to an incident and resolve it in the least amount of time as possible. If we can't resolve it, it enters our problem process where we can determine the source, possible fixes, and prevent the same problem from occurring in the future.

It integrates with a lot of other products. You can integrate it with ticketing systems and all sorts of software. There are links to software that allows it to be monitored. It's a monitoring system, so it makes sure that everything is up and running. You can have dashboards and just make sure everything is up, working, and functioning correctly.

the implementation of Operation Manager made it possible to centralize the events of several supervision tools such as sitescope, Network node manager or Nagios.

This is one of the big advantages of the product, the connectors developed by microfocus.

All the enrichment part allowed to reduce the processing time of support tickets. All the information was already present in the alarm.

We could have gone further with the connectors to the ticketing tools.

Translated with www.DeepL.com/Translator (free version)

It helps us the most with correlations of events and events handling; how we do that in SM9, it is a new way of working for us. I'm very pleased with it.

My customers are happy and satisfied with the monitoring capabilities that give them a more precise picture of company performance. The company can can improve and make changes according to the data that monitoring provides them.

We are able to better identify the root cause of an incident. It also reduces the number of tickets that we have received, because there is some correlation.

In Micro Focus OBM, everything was controlled at the node level and now everything can be controlled at the console level.