View impact of child service on parent service

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read

    • In the map view of an application service, the severity of a child service is propagated to its parent service.

    Before you begin

    Role required:
    • for application services, evt_mgmt_admin
    • for discovered services, service_mapping_admin

    About this task

    In the map view of a discovered application service, you can see that the severity of a child service is propagated to the parent service.

    An application service is affected by the severity of alerts that are directly associated with it and alerts on the CIs that are in the service. If the severity of a child service is higher than that of its parent service, on the map view the parent service shows the severity of the child service. In the map view, the Impact Tree list shows the CIs. The color of the CIs indicates the alert severity. The child service is also affected by application services that are under it.

    Figure 1. Example where the parent service shows the severity of the child service
    Child service severity is propagated to parent service
    If a loop is created, for example, by connecting a parent service to a sub-service, this relationship can be viewed in the map view. The impact of this loop is not calculated and the Impact Tree does not display this relationship. For example, assume that there are three CIs, A, B, and C, where C is a sub-service to B and B is a sub-service to A. The relationship of the A connected service to C is displayed in the map view. However, this relationship is not shown in the Impact Tree.
    Note:
    A message appears in the system error log in the following format, where the sys_id of the service and the node changes accordingly: Found loop in ServiceId:[sysId], and node:[sysId]. Removing this relation to avoid impact loops

    For example, Found loop in ServiceId:409d4fd59f030200fe2ab0aec32e705c, and node:df5cf6159f030200fe2ab0aec32e70a2. Removing this relation to avoid impact loops

    Click a service or CI to see the alerts that are associated with it. For example, if you click the high-level application service, the alerts that are associated with it are displayed in the alert area under the Map View. The alerts listed are those of the selected service. Alerts of child-services are listed when those services are selected.

    Figure 2. Example of alerts listed under the Map View
    Alert list in the Map View

    Procedure

    Open an application service map:
    1. Navigate to Event Management > Services > Application Services.
    2. Select View Service next to the service.
    3. On the right-hand panel, select Impact tree.
    4. On the lower panel, select Impact.

    Result

    In the service map, you can visually verify that the service health of the sub-service is rolled-up to the parent service. At the bottom of each icon of an impacted CI is a colored bar that represents the severity of the alert. This color bar also displays in the bottom bar of its parent service. For manual cluster configuration, you can modify the Application Impact and Application Cluster Member.