Investigating ML-based primary situations
Related topics
Investigating ML-based independent situations
Investigating ML-based situations that impact multiple services
As an operator or a site reliability engineer (SRE), use the ML-based primary situations to:
- Investigate issues faster by grouping related issues
- Reduce redundant alerts
- Focus on probable root causes
- Take actions that affect all related situations in one go
A primary situation is a grouping of multiple related open situations that occur due to a common issue and impact multiple services across the service hierarchy. Instead of analyzing each situation individually, operators and SREs can investigate the primary situation to understand the broader context and take corrective actions efficiently. This approach streamlines troubleshooting, reduces redundant alerts, and highlights the root issue affecting multiple services.
For a primary situation to be created, all the involved situations must be linked through shared CIs or relationships, regardless of the impact direction. Also, at least two events are required on each participating service. These are then grouped into a primary situation based on topological links.
Example
Consider a scenario where a network switch failure occurs in a shared infrastructure of a data center. This switch is a configuration item (CI) that supports multiple business-critical services such as login service, billing service, and payment portal.
Due to the failure, each of these services experiences degraded performance or outages, triggering separate situations in BMC Helix AIOps. As all these situations involve the same network switch CI, and are linked through related CIs in the topology.
automatically groups them into a primary situation.
To investigate a primary situation
- On the
console, click Situations.
All situations that occurred in the last 24 hours are displayed in a hierarchical view. Primary situations are indicated by the
icon.
To learn more about primary situations, see Situations-overview. - Expand the primary situation group to view all related situations.
Identify one or multiple root cause situations indicated by the target
icon.Click the primary situation and view the following details on the situation details page:
Situation name, severity, priority, last modified date, and status
Incident ID: Click to view the incident (if created), or click Create Incident to create an incident in BMC Helix IT Service Management (requires a subscription to BMC Helix IT Service Management).
Name of the impacted service: Click the service name to view service-level details in a new tab.
Related situations: Lists all grouped situations under the primary situation.
Show Notes: Opens the Logs and Notes panel. View logs and notes associated with the situation.
In the Related Situations section, identify the root cause situation (indicated by the
icon) and analyze attributes such as time of occurrence, number of similar situations, number of related events, type, severity, priority, status, and incident ID.(Optional) Click a situation name or related events link to drill into more detail.
(Optional) Click the Incident ID link to open the incident in BMC Helix IT Service Management.
(Optional) Click the action menu
to perform actions on a situation.
For more information, see Performing-situation-actions.
Where to go from here
To perform additional actions on a situation or on the events included in the situation, Performing-situation-actions.