Low granularity not working as expected
search cancel

Low granularity not working as expected


Article ID: 129617


Updated On:


CA Service Operations Insight (SOI)


We have modeled many services in SOI with CI's coming from UIM (via standard UIM connector). In these services you will find multiple redundant pairs of CIs; some being actual computer systems, some so-called business logic CIs represented as File object CIs in SOI. These business logic CIs are actually children of the parent computer system CIs. The relation can be compared with a Port being the child CI of a Router or Switch. In the case where you would find six CIs in a service, there would be three custom policies defined on the service. One custom policy per redundant pair of CIs. See attached screenshots. Alerts in UIM can be asserted in SOI on the parent CIs as well as on the children CIs. Typical alerts on parent CIs would be memory or disk problems on the computer systems. Typical alerts on the children CIs would be errors that are found in the log files that are monitored via UIM robots. Not all child CIs have been modeled. Only the ones that the customer finds most important. All other child CIs can be found in the CI Staging table, but are not modeled. To be able to see any alerts on those child CIs we have enabled Low Level Granularity on the services. All Alerts of the Child Cis, either modeled or unmodeled appear now on the modeled Child CI and not on the modeled parent CI.


SOI 4.0 SP2
SOI 4.2


This is working as designed.
If you explicitly sets low-granularity mode, it will treat a CI and all its child CIs as a single unit. So whether you select a CI or a child CI (irrespective of whether it is modelled or not), you will see all the alerts on the CI as well as all its child CIs.

Additional Information

Escalation policy and event policies only can create with alerts not with CIs if escalation polices criteria meet with alerts then it will be triggered.

So, here it does not matter if it is parent or Child CIs.