Identifying the impacted CI nodes from CI topology view

When a service is impacted, operators or site reliability engineers (SREs) need to have the complete visual representation of the CI topology. This information is especially useful if the service design is dynamic and complex.

The CI topology in BMC Helix AIOps is a structural map that shows the interconnectivity between various CI nodes of a service model. This map helps the operators: 

  • Visualize the interconnection between CI nodes as topology mapping with the impacted and nonimpacted paths and nodes.
  • Identify the impacted nodes and impact path and to work on a resolution immediately.

Related topics

Service-health-score-and-health-timeline

Monitoring-service-health

BMC Helix AIOps performs an automatic CI topology mapping and visually represents the relationship between a service and its nodes with node details, such as events, incidents, and changes end to end. The end-to-end topology map is capable of presenting the complete picture of all CI elements starting with the infrastructure nodes, network devices, hosts, clusters, namespaces, and all the application nodes of a service. The topology visualization supports grouping and ungrouping of nodes of same CI kinds and clearly identifies the impacted node with additional drill-down views to investigate the impact cause.

Scenario

At APEX Global IT, there is an end-to-end interconnected E-Banking application service with child nodes, such as a Core-banking infra, a Kubernetes(K8s) cluster with multiple pods, a deployment node, a host named Host A associated with a Namespace, and some network devices. The service has turned into a critical health state on a particular day.

Susan, an operator at APEX Global IT, views the service details and uses the CI Topology option to view the complete map, and expands the nodes and grouped CI kinds to identify the problem nodes. Susan sees that the deployment node has turned into a critical state, which has impacted the Core-banking infra, but not Host A. It will eventually impact the overall E-Banking service, as shown in this flow diagram.

CI_Topology_Example.png

To view and identify the impacted nodes using CI topology

  1. On the Services page, click a service name to view the health and the impact on the service.

  2. Click CI Topology to view the topological map of the service CIs and identify the impacted nodes.
    The CI topology nodes are displayed according to the node impact severity status along with all the CI categories defined as part of the service model.

    Tip

    If you have a large number of CIs in a service topology, use the search box to locate a particular CI. When the CI is located, it is highlighted. If a filter is already applied and CI is not present in the filtered view, the CI is  searched in the entire CI topology. When the CI is located, it is highlighted and the filter is cleared.

  3. (Optional) To change the topology map orientation, use the hierarchy list and select any of the options available.
  4. (Optional) If there are many nodes of the same CI kind in the map, use Enable grouping by CI Kind enable_grouping_by_ci_kind.pngto group the nodes of the same CI kind.
    Note that 10 or more CIs of the same kind are automatically aggregated together. If there are more than 10 CIs of the same kind, they are grouped as nine nodes plus one. The single node is a grouped node, which can be expanded to view the additional nodes as shown in the following image, where the Additional 'Software Instance' CIs node is an an aggregation of two more nodes. 
    ciTopology_group_23201.png

  1. (Optional) Select any CI node to view and analyze node-specific details. 
    You can view the list of impacting events, incidents, change details, and the services that are impacted directly or indirectly due to this node. From the Event Details summary pane, you can launch BMC Helix Operations Management to analyze the complete event details. In addition, if the CI topology is for the services belonging to an application instrumented by OpenTelemetry, the cross-launch link to the OTel Service Overview dashboard appears. For more information about the dashboard, see OTel Service Overview dashboard.

  2. (Optional) Use the advanced filter options to query for a single node or part of the topology map that you are interested in viewing.
    The advanced filter is capable of displaying only the impact path and all the impacted CIs in that path.
    For example, if you want to query and view only the Host CI Kind, select Advanced filter > Kind > Host. If you want to view the nodes impacted by the causal node, select Advanced filter > Impacted CIs > Impacts.

    Tip

    Based on the length of the selected criteria and the available space for displaying, the filters are automatically tagged and grouped as +1 active, +2 active, and so on. You can click the tagged number to view the additional filters.

  3. (Optional) Use the various display options to maximize or minimize, drag or position, zoom in/out, and fit to center the topology map.


Where to go from here

Based on the health of and impact on a service, you can perform any of the following tasks: 

 

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