

Understanding Service Modeling › Service Modeling Terminology and Concepts › Service Concepts › Granularity
Granularity
CA SOI supports granularity at two levels: Normal and Low. Normal granularity mode represents an explicit modeling principle where alerts are presented in CA SOI only if all the impacted CIs are included in the model. For example, a computer system CI that is running many service-supporting resources. When the service granularity is Normal, you include all the resources in the model to show their alerts as impacting the service.
Low granularity mode represents a mixed modeling principle where you manage the service granularity as follows:
- You include only the parent CIs and no associated child CIs in the service. In this case, parent CIs act as aggregators for all alerts that affect them directly or indirectly through their commonly related resources. For example, consider the same scenario of a computer system running various service-supporting resources. In this case, you only include the computer system, and any alerts affecting any of the resources hosted on the computer system are aggregated to the computer system.
- You include the parent CIs and specific child CIs (not all child CIs) in your service. In this case, any alerts that are directly associated with the included child CIs are aggregated to those CIs. The alerts that are associated with the nonmodeled child CIs are aggregated to the corresponding parent CIs. For example, you include a computer system CI and its child CPU CI in your service model. If any CPU-related alert comes in, it is associated directly to the CPU. Any other alert not directly associated with the CPU gets attached to the parent computer system CI. Therefore, including granular child CIs does not change the low granularity of the service model for excluded child CIs, enabling mixed-mode low granularity modeling.
Copyright © 2013 CA.
All rights reserved.
 
|
|