IP Connection relationship discovered between Wireless Controller and servers

[Annie7]

ServiceNow Discovery creates an IP Connection relationship between Wireless Controllers (or WAP switches) and Servers. That causes Application Servers to appear as impacted in Change tickets when changes are made to Wireless Access Points (WAPs) or Wireless Controllers.

Does anyone have same situation in the organization? Is the IP Connection relationship setup correctly between a wireless controller and servers? 

Is there any best practice we can consider either to update discovery patterns or identification rules to prevent creating the relationship or  create customize script for change to stop the wireless change populates server impacted

[Simon Hendery]

Here's the evidence it's been cut and pasted without any thought or any attempt to check it's legible:

[MaxMixali]

Hi, I think you have a lot of time to wast. it's depend of my editor. Sublime Text, anyway. nice to meet you 

[Vincent_Shaw]

Yes, this is a common issue. IP Connection relationships often create false positives for server impact. Best practices: adjust discovery patterns or identification rules to exclude Application Servers from relationships with Wireless Controllers/WAPs, use discovery filters to limit unnecessary connections, and consider a custom script or impact rule to prevent server impact updates from wireless changes.