What is our primary use case?
- To monitor the complete IT infrastructure.
- To consolidate various products into one and various screen NOC were using to monitor the environments into one single screen, so they can act quickly on the issues and resolve the issue faster.
- Correlate the events from servers, network switches, routers, and present single or few events with the help of correlation techniques stream-based event correlation and topology based event correlations to reduce number of events, so NOC can find root cause more quickly and help with the ROI.
- Migration from Operations Manager of Linux to Operation Bridge products.
What is most valuable?
Single pane of glass. NOC has to view only a single screen to monitor the entire infrastructure. All events can be seen on single screen and they integrate well with other products.
Well integrated OMi with Network Node Manager (NNM), Operations Bridge Reporter (OBR), Operations Manager for Linux (OML), and Operations Connector and Universal Discovery to correlate events using SBEC event correlation. Event correlation helps to consolidate and reduce event counts, so operators can act quickly and resolve the issue in a timely manner.
It has the capability to display overall health of the infrastructure and is very useful for executive reports on the health of the infrastructure.
How has it helped my organization?
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.
What needs improvement?
Topology base event correlation. Topology-based event correlation does not work well with NNM events. NNM does not understand well and collect information needed to correlate the events. Separate active and history tables from one single table and improve performance. It should be improved to view more than 100K events from closed browsers without impacting performance. QA of the products should be thorough before it is released and documentation lacks the information needed to implement the products, upgrade the products from one version to next version, and there is integration with other products. If events goes beyond 100,000, performance is degraded and sometimes the browser freezes.
For how long have I used the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and technical support?
Technical support is good, but it could be improved.
Which solution did I use previously and why did I switch?
No, we are migrating from OML to OMi.
How was the initial setup?
Initial setup was straightforward and integration was easy.
What about the implementation team?
What was our ROI?
What's my experience with pricing, setup cost, and licensing?
Which other solutions did I evaluate?
What other advice do I have?
The product is great, but it could be improved.
Which version of this solution are you currently using?
Find out what your peers are saying about Micro Focus, Microsoft, BMC and others in Event Monitoring. Updated: July 2021.
521,817 professionals have used our research since 2012.