Use PDIs? Take our 5-minute survey to help shape the PDI roadmap.

Manual End points - CSDM - "cmdb_ci_endpoint_manual"

Suneelkumar9381
Tera Contributor

10 hours ago

Hi ServiceNow Community,

 

I have a few questions regarding Manual Endpoints and their role within the ServiceNow CSDM structure. I would appreciate any guidance or best practices from the community.

  1. Manual Endpoints:
    Could someone please explain the purpose and use cases of Manual Endpoints in the CSDM structure?

  2. Multiple Manual Endpoints:
    If multiple Manual Endpoints are created showing operational status as operational , could this lead to any issues or inconsistencies in the CSDM relationships or service mappings?

  3. Update Sets / Migration:
    Are Manual Endpoint mappings captured in Update Sets? If so, what is the recommended approach to migrate or replicate these mappings across instances, such as DEV → TEST → PROD?

  4. Service Watch:
    What exactly is Service Watch, and how does it relate to or potentially create these Manual Endpoint mappings?

  5. Troubleshooting:
    If unexpected Manual Endpoint mappings or relationship issues are identified, what would be the recommended approach to troubleshoot and determine what created or modified them?

Any documentation, best practices, or real-world experience around managing Manual Endpoints and Service Watch would be greatly appreciated.

Thank you in advance for your guidance.

0 Helpfuls
  • 77 Views
2 REPLIES 2

Christopher Hub
Kilo Sage

7 hours ago

ServiceWatch is the label used by ServiceNow's Service Mapping application.  It uses endpoints as the entry to a service map. (Ex: a load balancer service's IP + port).

0 Helpfuls

Pratiksha
Mega Sage

6 hours ago

Manual Endpoints: this exist to fill gaps that automated discovery can't reach

Multiple Manual Endpoints:a Manual Endpoint is scoped to the specific Application Service it was added to. If the same CI relationship is genuinely relevant to a second service, it has to be added there separately — it doesn't propagate automatically. That's why you see them in multiples. 

Update Sets / Migration:Manual Endpoint mappings are CMDB data records, not configuration/customization, so update sets generally do not capture them. My suggestion would be, Let each environment's own discovery/Service Mapping regenerate its endpoints from that shared logic rather than copying the data records themselves.

Service Watch: Before ServiceMapping this was the original name.  Still exist as data source. any CI or relationship created through the Service Mapping engine — including ones added manually while working inside a Service Mapping context get data source as ServiceWatch. 

Troubleshooting:This is tricky, I would start with basic created by/ updated by fields, look into audit history (if its enabled). I would suggest to look into the time stamp of cluster of these rather one of it. 

 

Hope it helps. 

 

Pratiksha

 

 

 

 

0 Helpfuls