I was contacted by someone regarding PeerSpot because she learned I was working with the Moogsoft tool.

I have been working with the Moogsoft tool for the last 3 years, and we handle the monitoring aspects with it.

I am currently working with Moogsoft, which is a monitoring tool, and we monitor different alerts, including DevOps alerts, Cisco alerts, DPA Dynatrace alerts, and Iceland alerts. We also create separation for servers and CM and IDs.

I also work on ServiceNow for incident management, receiving alerts from networking devices, and we monitor incident numbers before routing tickets to the appropriate tech teams.

We have deployed the tool. It’s an event correlation tool. Unlike tools like Splunk, which have their agents running on servers to send telemetry data and logs, Moogsoft operates differently. It collects data published from various telemetry tools and then handles the correlation. For example, if a web server goes down, Moogsoft will generate an alert indicating that the server is down. However, this alert alone may not provide meaningful insights. If the web server is down, there might be other related issues, such as database connection problems or API failures. This can overwhelm users with numerous alerts.

Moogsoft addresses this by filtering the noise and consolidating alerts into a single situation report. This way, users won’t be bombarded with alerts. Instead, they’ll receive a clear overview of the problem, identifying where it lies and what components are affected. This allows the Site Reliability Engineer to understand the situation better. Once a situation is identified, you can define workflows. A workflow might involve an automated repair plan that outlines specific actions if certain conditions are met. If action A is performed, then feedback will dictate the next steps. We have deployed Moogsoft for an automobile client and a bank in Singapore.

We were looking to replace the product we have, which was Moogsoft. However, the project got canceled, so we are not looking anymore. While we are looking for another solution, as of right now, management decided to keep it. So maybe in the next financial year, it will be a topic again. Still, we are not pursuing it anymore.

We are a service provider. We have the product under an MSP license. We offer this solution to our customers internally within the group and company. We are also using it for our few business units.

People use Moogsoft to filter out alerts in their NOC and IT service management.

Moogsoft is mainly used for internal network and storage monitoring, event and alert management, and as an observability platform.

I'm using this tool as a MoM tool, manager of manager. We have integrated a lot of monitoring tools, enterprise monitoring, infrastructure monitoring, and database monitoring tools with Moogsoft to provide one unified console to the NOC guys so that they don't need to jump around on multiple tools to view the issues. Through Moogsoft, using a single layer and a single screen, they can see all the issues and they can act. 

Further, Moogsoft is integrated with the ticketing tool ServiceNow. We are converting those alarms into tickets for further actions on resolving the issue.

We are developers, integrators, and consultants. We do everything.

Moogsoft is primarily used by our clients for event management.

Our primary use case is to reduce support request noise so that we can monitor and identify real issues rather than symptoms so we will be able to create tickets out of that with ServiceNow and enact more effective solutions. Moogsoft is a companion to how we envision using ServiceNow in an integrated fashion to improve the handling and efficiency of ITSM (IT Service Management).

I work with numerous products from old management framework products such as Tivoli to the latest products.

We are trying to migrate from Netcool/OMNIbus to Moogsoft for our customers.

We primarily use Moogsoft for our customers, who are telecom operators in a different country. We use it for monitoring the alarm extension of different components.

I have 17 years of experience in the telecom industry. I have had many roles including operations, installation, commissioning, and maintenance.

I think they are coming up with advanced features, but what happens is, ServiceNow is being used as an ITS solution. Some of our customers receive repetitive error messages due to a common root cause. With ServiceNow, that doesn't get classified under a single ticket. Rather it comes as multiple error messages. With Moogsoft, we do a clustering around it, and through the initial aggregation to understand this problem, it is solved. Moogsoft reduces excess noise. Hence we wanted to cluster the issues so that when the help desk or the IT administrator or the service administrator is looking at the issue, we have better visibility to look at where it is, and also be able to predict level-two issues and take corrective actions.

I don't know the exact number, but we have quite a few customers using Moogsoft. From my understanding, there are more than one million users, but I could be wrong.

Our clients required much-needed improvement in the detection and remediation of incidents, ensuring continuous service delivery, so they opted for Moogsoft AIOps.