Stand by load balancer not getting discoveredIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> When the customer's network has multiple load balancers and a stand by setup, can we expect to see the standby load balancer on the business/application service? ResolutionWhen an 'HTTPS endpoint' is chosen while creating a map, a Fully Qualified Domain Name would be fed as the entry point.Once the right is FQDN has been provided, the DNS probe determines the IP address mapped to the FQDN.The load balancer services table in the ServiceNow's instance would be referred to determine the right LB serving or configured for the IP address determined above.Once the LB is determined, the vertical discovery process continues until the map is filled with the right set of CIs that are expected to serve a business/application service.The Active Load Balancer that would be serving the request is expected to be shown on the map but the standby load balancer will not be shown on the map. It is by design. An example map looks like the below -