Service Mapping creates duplicate Candidate Entry Points

[RajeshGummadoju]

Hi All,

We initially created Service Maps from the potential candidates generated by Load Balancer Services. After some point of time we still see there are list of candidates for the same entry point which is already mapped.

Any suggestions on how we can strategies this.

Example:

Initially candidate entry point  https://172.1.1.1:443 created a application service and we mapped it.

Later when we check Candidate Entry points table we still see https://172.1.1.1:443 is present.

Below document doesn't have much information about it.

https://docs.servicenow.com/en-US/bundle/vancouver-it-operations-management/page/product/service-map...

Thank you,

Best Regards,

RajeSh

[SwarnadeepNandy]

Hello @RajeshGummadoju,

• One cause could be that the Load Balancer Services discovery pattern does not remove the candidate entry points after they are mapped to an application service. This can result in duplicate entry points in the Candidate Entry Points [sa_lb_service_candidate] table. To fix this, you can manually delete the duplicate entry points from the table, or modify the pattern script to delete them automatically. You can use the Service Mapping : Entry Points not being removed from Endpoint tables after mapping - ServiceNow article as a reference for this solution.
• Another cause could be that the entry point attributes are not configured correctly for the application service. This can result in multiple entry points with the same or similar attributes being discovered and mapped to the same application service. To fix this, you can review and update the entry point attributes for your application service, and make sure they are unique and consistent. You can use the Entry point attributes - Product Documentation: San Diego - ServiceNow article as a reference for this solution.
• A third cause could be that the entry point types are not defined properly for your application service. This can result in entry points of different types being discovered and mapped to the same application service. To fix this, you can create custom entry point types for your application service, and specify the criteria and rules for identifying and mapping them. You can use the Create entry point types for Service Mapping - ServiceNow - Now Support article as a reference for this solution.

I hope these helps you resolve your issue.

Kind Regards,

Swarnadeep Nandy

[RajeshGummadoju]

@SwarnadeepNandy Thanks for your prompt response. I agree with all your three points above mentioned.

In our scenario that was not the case, We are seeing the same entry point from same Load balancer being created though we have Mapped Application Service with that Entry Point and it is present in "sa_m2m_service_entry_point" table as well.

Is it OOB behavior or something we can remediate from our end.

Thank you,

Best Regards,

RajeSh