Concerns with Discovery populating data in 1000s of tables!!!

Suggy
Giga Sage

‎06-29-2025 06:40 AM

Hi All,

We are using Discovery for CMDB population.  It populates data in 1000's of tables.

 

What we actually want is to have Discovery populate data in only desired tables.

Data in tables like - Network adapter, Next Hop routing rule, Memory module, Disk, File system etc is of no use to us. Customer also checked with all their infra team members and they told that such data is not required for them.

 

Now customer is asking to stop Discovery from populating data in all such auxiliary tables. When we tried to tell them not to do so, as such data will be required in one or the other way or in future, they are asking use to give a use cases for all such tables.

 

Did you ever come across such a situation? How to handle this?

 

Infact when I myself started to think as a customer, I am also not knowing 'WHAT DO I DO WITH DATA IN such tables? Why should I have data in my CMDB TABLES which I dont need" 

0 Helpfuls
  • 268 Views
1 REPLY 1

Ram Devanathan1
ServiceNow Employee
ServiceNow Employee

‎06-29-2025 09:39 PM

Each table is filled in with details from a pattern.

 

simple solution would be to turn off the pattern but is it right to do this?

there are many considerations.

 

Turning off a pattern could impact downstream and upstream relationships, you may have to turn off multiple patterns. this can result in multiple issues of lack of visibility and have overall impact on monitoring (correlation), reporting, auditing, asset management, etc.

 

I find it odd you would say disks and FS are not important. Taking Disks as an example, here's some food for thought -

I have a server with multiple disks attached, for storage. Application A's data is on disk1 and Application B's data is on disk2. if Disks are not discovered at all, then when disk 1 has a problem, the alert will attach to the server, and the server CI will show as impacted - both App A and App B will show impact but in reality only App A is impacted. this will lead to unnecessary tickets, actions to be taken.

 

what's the real issue though?

 

to get an overall view, the customer can use our cmdb workspace and the cloud workspace.

 

0 Helpfuls