Building Service Models › How to Build a Service Model › Set the Granularity Level

Set the Granularity Level

You can change the granularity level to determine if you need to include all resources in the model for their alerts to be shown as impacting the service.

Consider the following:

• You can only change the model granularity of a service you are currently editing.
• You can change the default service model granularity for subsequently created services on the Global Settings page of the Administration UI.

Follow these steps:

1. Right-click a service in the Service Modeler.
2. Select Change Granularity and one of the following.

   Normal

   A normal granularity service model does not aggregate alerts from child CIs not included in the service model.

   Low

   A low granularity service model aggregates alerts from child CIs not included in the model.

   Note: You cannot include an unmodeled CI in any service if the CI is to impact a modeled CI in low granularity mode. This is because the alerts for that CI are attached to an existing model and the low granularity level looks for unmanaged alerts.

3. If a confirmation dialog opens, click Yes.

A low granularity service detects whether unmodeled child CIs exist that are related to modeled CIs and immediately begins propagating impact from those CIs. You can tell when a service is low granularity by the following indicators:

• An ‘L’ character appears in the Information column of the Services tab.
• Granularity displays as LOW in the service model tooltip on the Topology tab.
• Granularity displays as Low in the Information tab when you select the service.

When CA SOI detects that a low granularity service contains CIs with unmodeled child CIs and associated alerts that are propagating impact, a icon appears next to the parent CI to indicate this fact. The color of the parent CI itself does not reflect the impact of the alerts; instead, the impact is propagated upwards on the CI's parent, and ultimately, the service.