Incident.MOOG by Moogsoft provides a new approach to IT by enabling proactive, situationally aware, collaborative operations and service assurance processes. Incident.MOOG accounts for the key drivers of IT incidents and builds upon existing tools and processes. Incident.MOOG automatically recognizes the existence of an incident, identifies the causal and impact indicators of the incident, and engages the stakeholders collaboratively around the incident. Incident.MOOG requires no changes to existing tools or processes, and it requires no rules, business logic, or models to maintain.
Check it out here: Service Assurance Productivity with Incident.MOOG Minky v1
- Scenario 1: Explore Incident.MOOG
- Scenario 2: Explore the Situation Room
- Scenario 3: Understand the Value of Incident.MOOG Through Customer Experience
- Incident.MOOG v5.x
- PC workstation at Google Chrome
- Situationally enable and orchestrate stakeholder resources and remediation activities appropriately.
- Identify incidents and their causes before or at the same time as the customer is impacted.
- Use previous knowledge to restore service more quickly.
- Use similar situations to help identify recurring issues.
- Use the Situation Room to invoke third-party tools (such as EMSs, diagnostics, and other operations support tools) to restore service more quickly, shaving minutes off of diagnostics processes.
- Massive reduction of actionable issues for support operations resources from more than 1.7 million raw events to 38 situations (a reduction of 99.9999%) without models, previous behavior knowledge or topology rules.
- Explore a pair of situations which, because of fewer actionable issues, are easy to assess, showing a causal and collateral scenario that would never have been detected by using traditional processes and tools.
- Inference of situations that offer causal and collateral indicators that, in the real world example, would have saved 6 applications support people 45 minutes of forensics work and would also have enabled awareness of the issue 1 hour before the first support issue was received and assigned.