Loggregator Network Communications

This topic describes Loggregator internal network communication paths with other Pivotal Application Service (PAS) components.

Loggregator Communications

The following table lists network communication paths for Loggregator.

Source VM Destination VM Port Transport Layer Protocol App Layer Protocol Security and Authentication
Any* loggregator_trafficcontroller 8081 TCP HTTP/WebSocket OAuth
Any VM running Metron doppler 8082 TCP gRPC over HTTP/2 Mutual TLS
loggregator_trafficcontroller doppler 8082 TCP gRPC over HTTP/2 Mutual TLS
loggregator_trafficcontroller uaa 8443 TCP HTTPS TLS
loggregator_trafficcontroller cloud_controller 9023 TCP HTTPS Mutual TLS
loggregator_trafficcontroller (Reverse Log Proxy) doppler 8082 TCP gRPC over HTTP/2 Mutual TLS
loggregator_trafficcontroller (Route Registrar) nats 4222 TCP NATS Basic authentication

*Any source VM can send requests to the specified destination within its subnet.

Starting from ERT v1.11, Metron does not use the UDP protocol to communicate with Doppler. Starting in PAS v2.0, Doppler no longer uses the UDP protocol or the HTTP/WebSocket protocol.

Consul Communications

PAS components call out to Consul for service discovery. For more information, see Consul Network Communications.

BOSH DNS Communications

Application containers look up services using the BOSH DNS service discovery mechanism. To support this lookup, BOSH Director colocates a BOSH DNS server on every deployed VM. For more information, see BOSH DNS Network Communications.

Create a pull request or raise an issue on the source for this page in GitHub