Indicator Source - Data Collector Limit

[Kuldeep Kumavat]

Hi All,

We have a daily CMDB Job containing around 30+ Indicator Sources out of which 7 are failing due to data limit. Few of them are basic queries like collecting all Active CI (active=true as the only condition) and a couple of them are script based. The business wants active CIs as the whole set for many of reports, so cannot filter any further.

We have the max_row_count_indicator_source property set to 75k records. But due to recent a import in CMDB the count of CIs went upto 190k. So, that the job is failing to collect data for 7 Indicator Sources as they are fetching more than 75k records as defined in the property.

The question I have are:

1. If the property is increased to collect say around 200k records, what kind of impact it can have on performance (considering few of the indicator sources are script based and also the count of CIs can increase in future).

2. Is there any other approach you can suggest to resolve this issue.

We are upgrading to Jakarta (from Helsinki), so we have not yet explored the whole set of New CMDB Dashboards.

Regards,

Kuldeep

[Josh Cooper]

You're not in terrible shape, luckily.  We have some customers whose CI counts get into the millions, and some of those double digit millions.

The official answer from ServiceNow development is that you may need to disable the main overall collector (i.e. all active CIs) and build a few different indicators like it, something like

"Active Servers"

"Active Computers" (not servers)

"Active Network Devices"

"Other Active CIs"

Then you can collect and add them together with a formula indicator.  Remember to turn off the "collect records".  It's probably not going to be useful information anyway.

[Kuldeep Kumavat]

Breaking down the indicator sources for different classes was the last option I had. I didn't thought of combining them through a formula indicator. This will save a lot of time and effort. 

Thanks a lot for the response.

Regards,

Kuldeep