Access logs hold the truth about every request. They record the IPs, timestamps, headers, and the path of data through your proxy. But if you miss the internal port mapping, you lose the context. Ports define where the proxy routes traffic on localhost or inside the container network. Without them, your debugging is blind.
A proxy’s internal port is not always the external port you expose. Reverse proxies, load balancers, and containerized services often hide the real endpoint inside the network. You discover it by reading the host service configuration and matching it to the log entries. For example, a container might expose port 8080 internally, but your proxy forward shows traffic on 443 externally. The log line will reveal the handshake only if you capture full request–response metadata.
To make logs useful, configure them to include the upstream host, internal port number, and request details. In Nginx, use $upstream_addr with $request_uri in your log format. In Envoy, enable access log fields for downstream and upstream addresses. Match these against your deployment maps to see exactly where traffic lands.