Need help mapping F5 XC / Distributed Cloud services in ServiceNow Service Mapping

MorZ
Tera Contributor

16 hours ago

Hi all,

We need assistance with mapping applications that are routed through F5 XC / F5 Distributed Cloud in ServiceNow Service Mapping.

Current situation:

  • The application is accessed through an external URL.
  • Traffic is routed through F5 XC HTTP Load Balancer.
  • Backend targets are configured in Origin Pools.
  • The customer cannot provide direct MID Server access to the backend/internal addresses.
  • We tried building a custom Pattern using F5 XC API, but were not able to complete the mapping successfully.

Our goal is to map the service chain:

 

 
External URL → F5 XC HTTP Load Balancer → Origin Pool → Backend Servers
 
 

We attempted to retrieve the data through F5 XC API, including HTTP Load Balancers and Origin Pools, but we are unsure how to properly translate that API data into Service Mapping relationships / CMDB relationships.

Questions:

  • Has anyone implemented Service Mapping for F5 XC / Distributed Cloud?
  • Is F5 XC supported in any standard ServiceNow Discovery or Service Mapping capability?
  • If not, what is the recommended approach?
    • Custom Pattern?
    • REST integration to populate CMDB?
    • Custom CI classes / relationships?
    • Manual service modeling?
  • How should we handle the mapping when the MID Server cannot directly reach the backend servers?

Any real-world experience or implementation guidance would be very helpful.

Thanks in advance.

0 Helpfuls
  • 130 Views
1 REPLY 1

pr8172510
Tera Guru

46m ago

Hi @MorZ,

F5 Distributed Cloud (XC) is not supported by an out-of-box Discovery Pattern or Service Mapping pattern.

  • Service Mapping requires MID Server visibility and connectivity to discover application dependencies automatically.
  • If the MID Server cannot reach the backend servers, Service Mapping cannot perform standard top-down discovery of those dependencies.
  • In this scenario, the recommended approach is to use the F5 XC APIs to import topology information and populate CMDB relationships through a custom integration.
  • Typical relationship
    • External URL → F5 XC HTTP Load Balancer
    • F5 XC HTTP Load Balancer → Origin Pool
    • Origin Pool → Backend Server

If backend infrastructure is not discoverable from the MID Server, a combination of custom REST integration, CMDB relationship creation, and manual service modeling is generally the recommended approach rather than Service Mapping alone.

Service Mapping dependency discovery relies on MID Server access to the target infrastructure, so limited network visibility will also limit automatic service mapping capabilities.

0 Helpfuls