Monitoring and investigating situations

BMC Helix AIOps correlates events collected from multiple sources across infrastructure, applications, network resources, and monitoring solutions from different vendors into situations. The events from the same or different hosts are correlated based on their occurrence, message, signature, topology, or a combination of these factors into different situations. Situations created by using the AI/ML-based technique are known as ML-based situations in BMC Helix AIOps. 

Situations are correlated by filtering raw events and other situations based on:

  • Problem pattern and event signatures
  • Analysis of the message content
  • Sequence of the event from the same node or different nodes of a service hierarchy
  • Time and day of occurrence, and so on

An event's signature is derived from the name of host from which the event originated and the event message. Based on the type of correlation, situations are categorized into independent, primary, or similar situations.

Related topics

Roles-and-permissions

Configuring-ML-based-situations



The following diagram shows how situations are created from raw events:

situations_workflow.png

BMC Helix AIOps can analyze hundreds of thousands of raw events in near real time to create situations. Here are some of the major benefits of using ML-based situations in BMC Helix AIOps:

Advanced noise reduction and reduced mean-time-to-resolve (MTTR) issues

  • The algorithm uses an event signature to analyze topological and temporal relationships to create highly-contextualized situations.
  • BMC Helix AIOps uses advanced configuration settings to determine the aggregation window and groups situations into primary, related, and similar situations.
  • BMC Helix AIOps console provides options to perform event operations on individual events and situations.

Direct path to probable or root cause of the impact

  • The algorithm analyzes, ranks, and displays the topmost situations.
  • Situations link directly to the impacted service to help with root cause analysis.

Direct path to the change requests in BMC Helix ITSM

  • The algorithm considers change requests from BMC Helix IT Service Management for various CIs to create situations in BMC Helix AIOps. Change requests from CIs that are not associated with a service name are ignored. 
  • Situations link directly to the impacted service to help in faster root cause analysis. In addition, there is a link to view and manage the changes from BMC Helix IT Service Management.
  • Only the changes from the last five days are shown in BMC Helix IT Service Management.

Automated problem resolution

BMC Helix AIOps provides the ability to remediate situations through BMC Helix Intelligent Automation.

The following diagram shows high-level process  for managing situations in BMC Helix AIOps:

situations_workflow_with_changereq.png

Learn about the advanced monitoring and analytical capabilities by using the following topics:


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*