Service Mapping — How to handle dynamic ports for microservices

Kiran Gundap5
Tera Contributor

Hi ServiceNow Community,

We’re building Service Maps for several applications. In some cases, the infrastructure includes microservices servers that do not have a clear entry point to discover/map from.

To include these servers in the service map, we are currently using the running service port on the server along with the API path/name—for example:
<ServerName>:<port>/api/<name>

Issue: The service port is dynamic and changes after each service restart, so we have to update the port frequently to keep the service map accurate.

Has anyone dealt with this scenario before? If so, what is the recommended way to handle dynamic ports in Service Mapping  so we don’t need to manually update ports after restarts?

Thanks in advance.

0 REPLIES 0