Best Way to block the data insertion for Discovery tables

[Shubham_Jain]

I would like to block the data insertion for discovery tables as these tables does not gives any valuable data and it clutter the CMDB. 

Some example table is: Dscy_route_next_hop table. 

Suggest me best apporach to block the data insertion. 

The important point is that this should not write an message on system logs or any other tables in the platform. It just block the insertion. 

[Shubham_Jain]

@VivekSattanatha I am trying level best to convince client that not to block any insertion of data especially when it is coming from discovery. However, the clear requirement is to block the data and client do not want CMDB to be full fill with junk or cluttered data which has not value. 

And this is not applicable only for network tables, we have seen this data gets full when server or computer getting discovered so applying only network would not be best solutions 

[VivekSattanatha]

These entries will exist in any hardware-level tables from routers or switches, as they are used to map routes between devices. While it is possible to disable them, I do not recommend doing so. Instead, consider an alternative method to restrict user visibility of this data rather than deleting it.

[Shubham_Jain]

@VivekSattanatha I completely agree with you and echo the same. 

however the client requirement is to block the data and they do not want any data in these tables. 

kindly share the way to block the data. 

[VivekSattanatha]

Disabling the SNMP routing and next hops pattern would stop creating records on that table