Over the last year, I’ve heard many compelling reasons why customers want to reevaluate their legacy event managers.
One of the most common questions I’m asked is, “can Moogsoft replace Netcool?”
On September 17th, I’ll be hosting a webinar on that topic. Here’s a preview of what I plan to discuss.
First, the driving factors. It is usually a combination of circumstances that lead an organization to either replacing or extending the solution they’ve used for many years. It’s not an easy decision.
When customers purchased their legacy “Manager of Managers” the goal was to unite all the diverse event sources into a single stream and, when problems happened, quickly determine the single point of failure using correlation and root cause analysis.
If this goal was met today, IT operations would be running at peak efficiency and you would always know about outages or service degradation before end users.
So, when is it appropriate to “rip-and-replace?” Compelling reasons like business growth; changing business demands, and building out for the future are often the tipping point for making a wholesale change.
That’s because, in organizations facing expansion as well as change, the legacy Manager of Manager can’t keep up. Yesterday’s MoM is impeding IT’s ability to stay current with business growth.
During the webinar, I will show how Moogsoft has replaced legacy systems in this scenario. For example, Incident.MOOG is enabling one customer to handle 10 times the event volume – literally hundreds of millions of events per day. The customer is also able to respond faster to business demands and do it without hiring more staff to write rules, as they have been able to reduce the amount of rules they maintain by 80%.
On the other hand, some of our customers come to us recognizing that they are missing a key ingredient in effective event management: cross-domain visibility.
They have several event managers, each working reasonably well in its own silo. However, operations can’t respond quickly because of the challenges in coordinating their work across different silos. They want to improve service quality and operational metrics.
This is not necessarily a rip-and-replace scenario. Rather, Incident.MOOG can act as the Manager of Managers. Incident.MOOG exposes relationships between events, unifying silos of data and identifying situations across systems to help teams identify problems faster and restore service more efficiently.
There are other scenarios as well. I invite you to join me in our nextwebinar on September 17th as we walk through scenarios in more detail and answer your questions about how our customers are implementing Incident.MOOG.