Is it possible to set data source precedence between serverless and ip address discovery schedule

[Community Alums]

Hi Everyone, 

We are encountering an issue with fluctuating CPU count values; when the IP address discovery runs, it reports different values compared to the serverless Kubernetes discovery. We want to prevent this inconsistency by giving higher precedence to the IP address discovery. Is this achievable? Currently, the out-of-the-box data source precedence is available with ServiceNow, service mapping, SCCM, etc., but not between different types of discovery schedules like IP-based and serverless discovery. Can anyone provide insights. 

Regards, 

Srinija

[Runjay Patel]

HI @Community Alums ,

Answer is no, you can not do so as discovery source for both type would be "ServiceNow". Only way to handle here is exclude the ip list from discovery schedule from where you dont want to update the ci.

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.

Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------

[Community Alums]

Hi @Runjay Patel, 

Thanks for the response. I don’t think excluding ip address will solve the problem  because regular discovery is ip address based and serverless is api based. In api based discovery, I don’t think we can exclude Ip address. 

Regards, 

srinija

[Pratiksha]

What do you mean by ip address discovery? Can you explain the issue in detail? 

[Community Alums]

hi @Pratiksha  , 

Ip address discovery is the regular discovery where we give ip address as an input to trigger the discovery. 

Regards, 

Srinija