Duplicate Availability Zones, Cloud Disk Types and Google Datacenter CIs during GCP Discovery

[sch]

Hi Everyone

we have around 910 service accounts(projects) and 40 data centers in GCP environment. During GCP Discovery, ServiceNow end up creating Availability Zones(915323), cloud Disk Types(481140), Google Datacenters(35510). Data in these tables looks like duplicate entries but have different relations.

Question-

1.Is there any specific calculation behind these numbers?

2.Any one implemented GCP Discovery ? Do you relate these numbers?

3. With this huge numbers, Discovery Home is not even loading data for Google.

4.Is there any workaround to reduce these numbers just like Old Hardware Type Vs New Hardware Type model?

5.It is even impacting users creating change, incident and problem and trying to select a Ci as it is taking a while to open the entire list, end user is getting confused with duplicate entries(i mean i understand they are different for each service account)

6.Unless we go check relations, these specific classes do not have any other fields which help us understand for which service account vs availability zone vs datacenter

Thanks

Sirisha

[Ram Devanathan1]

for each project, separate datacenter records are created- this is for some legacy reasons in the model

going by this if you have 35k or so DC records it is around the mark

910*40 = 36400

you can reduce the number of datacenters in the schedule if not all are used - it will save time.

The reason for page loads being slow could be indexes as well as large logs. please ensure to have trimmed logs and turn off any debug logs if not wanted.

please check for stale unused CIs that could also be adding some overhead.

where does end user have to deal with regions - they deal with with CIs only.

have you used the cloud operations workspace app in store - the cloud inventory dashboard can help to sort out the CIs into their regions and accounts and also the tables that are part of this app (called analytics tables name starting with sn_disco_cd) will give association of the resources to the right account/region.

Please raise support case for slowness issues.

[Laurent Dehove]

Hello

We encounter similar problem.

With all our project and datacenter, discovery creates 50.000.000 CI of class Disk type.

We need to discovers all these projects, and can't exclude datacenter  becasue they can be use in some projects.

This huge number of CI has a very bad effect on performance when using this class or more generic class like the cmdb_ci.

Why the CI 'disk type' are duplicated ? what is the use of this ? 

We understood at beginning that each type type will exist once, and have a relation to the availability zone where it is used.

[rkolosky]

Having these CIs duplicated per Google project and datacenter is a terrible idea. Had over 6.5M Hardware types that I had to spend 2 days auto flushing out. AWS and Azure cloud scans have a lot of image CIs, but not this order of magnitude. Hope this gets fixed soon. It makes a greenfield instance CMDB unusable in just a few hours.

[FLP1]

Hello All, jumping here as i would like to know if there is a document in the community that can explain the use case of all this data, if it is not very important information can we turn off their collection? how can this be done?

thank you!