Dynamic CI Group - missing some Service CIs

[dant]

Hello Everyone,

Some Dynamic CI Groups do not have all the CIs (Service CI) which are in the related CMDB Group. The total number of CIs in the CMDB Group is below the 10,000 threshold.

Any thoughts on why and what can be done to fix it?

Thanks in advance.

[Miklos Palfi]

Hi Dan,

there is a periodic update of the [svc_ci_assoc] table, which stores the DSG results. (A refresh can be triggered by viewing the service CIs manually.) There is a sys_updated_on timestamp, which in our case shows an update time during the night (between 21:00-23:00 o'clock). One of our issue is that we report on the results before this time, which causes a one day delay and in case of frequently changing items like cloud VMs it may cause missing items. (e.g. VM is already inactive the next time when the snapshot is taken.) We try now to find a timing sequence which provides us the best possible results.

Scheduled update is triggered by a job (see sysauto table or Schduled Jobs menü entry). 

Miklos 

[Mathew Hillyard]

The update of the Service Config Item Association table for Dynamic CI Groups is contained within Business Rules in each of the related lists on the CMDB Group record that is referenced within the Dynamic CI Group record. This uses a private script include so you will not be able to see how it is updating, nor track the progress of any updates. I would first check whether inside the CMDB Group you can see all the CIs you are expecting based on the queries defined. I would also examine the queries to ensure you do not have overlapping conditions (e.g. one query on a parent CI class and another on one of it's child classes) as I have seen confused or delayed results. 

However I will say that I have usually seen updates inside a minute, even when initially creating tens of thousands of Service Config Item Assoc records, and have never not seen CIs, unless the DCG limit of 10,000 has been reached. If you have done all of this and still do not have answers then it needs ServiceNow Support to investigate.

[Anuneeti Mathur]

Hi, 

I'm facing a similar issue. Did you get a resolution from ServiceNow for this?

Thanks

Anu

[pbels1]

We faced the same issue the only way to solve this was to create multiply CI group and refine the queries to limit the number of that would be in the group.  A report was create to get the count for the CI groups in question so they can be monitor to ensure that the 10,000 record limit was not breached.

[RubenFuertes]

Hi,

There is a way to increase this 10k but, although I have asked to servicenow for the limit, they have not been able to give me an answer. The property you need to change is sa.qbs.max_num_of_cis.

https://www.servicenow.com/community/common-service-data-model-forum/dynamic-ci-groups-default-numbe...

Also note that if you use Tags instead of Dynamic CI groups the 10k will be reduced to 5k.

https://www.servicenow.com/community/common-service-data-model/application-services-how-to-use-them/...

Regards.