Report Issues Edit

Gateway Access Logs

Access Logs

How to view access logs?

Ingress traffic to Cloud Foundry is proxied through the istio-ingressgateway pods which prints access logs to stdout. To view them:

kubectl logs -l app=istio-ingressgateway -c istio-proxy -n istio-system

Example access log line

{
  "app_id": "58d9bc59-3993-4541-90fb-efe8f20acab9",
  "authority": "app.example.com",
  "bytes_received": "0",
  "bytes_sent": "846",
  "downstream_local_address": "10.56.1.110:80",
  "downstream_remote_address": "203.0.113.4:13456",
  "duration": "3",
  "method": "GET",
  "organization_id": "28a72883-be4e-4124-9f79-f8429a2d1256",
  "path": "/headers",
  "process_type": "-",
  "protocol": "HTTP/1.1",
  "referer": "-",
  "request_id": "eb36b92b-f757-4ca3-b27c-cef2e7e06944",
  "requested_server_name": "-",
  "response_code": "200",
  "response_duration": "3",
  "response_flags": "-",
  "response_tx_duration": "0",
  "space_id": "9765ce8d-5098-4756-a270-490c32233e4a",
  "start_time": "2020-02-07T00:47:45.516Z",
  "upstream_cluster": "outbound|8080||s-d77075c0-5c71-4d93-8c39-b8311c19be5d.cf-apps.svc.cluster.local",
  "upstream_host": "10.56.1.111:8080",
  "upstream_local_address": "-",
  "upstream_service_time": "3",
  "upstream_transport_failure_reason": "-",
  "user_agent": "curl/7.54.0",
  "x_b3_parentspanid": "-",
  "x_b3_spanid": "dacd7b5fc2e62cb7",
  "x_b3_traceid": "a6a1631bae96ac75dacd7b5fc2e62cb7",
  "x_forwarded_for": "203.0.113.4",
  "x_forwarded_proto": "http"
}

Duration fields

The access log contains the following fields for duration in milliseconds

  • upstream_service_time: The time from when the gateway sends a request to the sidecar to when it recieves a response from the sidecar
  • duration: The time from when the gateway receives a request from the client to when it sends a response to the client to the last byte out
  • response_duration: The time from when the gateway receives a request from the client to when it receives a response from the sidecar
  • response_tx_duration: The time a response spends in the gateway

Determining App Latency vs Platform Latency

To calculate the time a request spends within the gateway subtract upstream_service_time from response_duration

Fields

The fields we use are defined by Envoy’s access logging format.

  • app_id: Cloud Foundry application GUID
  • authority: Authority (HTTP/2) or Host header (HTTP/1.1) of the request; see RFC7540 for more details
  • bytes_received: Body bytes received
  • bytes_sent: Body bytes sent. For WebSocket connections it will also include response header bytes
  • downstream_local_address: Local address of the downstream connection; see %DOWNSTREAM_LOCAL_ADDRESS% in Envoy docs
  • downstream_remote_address: Remote address of the downstream connection; see %DOWNSTREAM_REMOTE_ADDRESS% in Envoy docs
  • duration: Total duration in milliseconds of the request from the start time to the last byte out; see %DURATION% in Envoy docs
  • method: Method of HTTP request
  • organization_id: Cloud Foundry organization GUID of the application
  • path: HTTP request path
  • process_type: Cloud Foundry Process Type for the backend being routed to
  • protocol: Currently either HTTP/1.1 or HTTP/2. See %PROTOCOL% in Envoy docs
  • referer: HTTP Referer header
  • request_id: Unique ID for the request
  • requested_server_name: String value set on ssl connection socket for Server Name Indication (SNI); see %REQUESTED_SERVER_NAME% in Envoy docs
  • response_code: HTTP response code. Note that a response code of ‘0’ means that the server never sent the beginning of a response. This generally means that the (downstream) client disconnected; see %RESPONSE_CODE% in Envoy docs
  • response_duration: Total duration in milliseconds of the request from the start time to the first byte read from the app; see %RESPONSE_DURATION% in Envoy docs
  • response_flags: Additional details about the response or connection, if any; see %RESPONSE_FLAGS% in Envoy docs
  • response_tx_duration: Total duration in milliseconds of the request from the first byte read from the app to the last byte sent downstream; see %RESPONSE_TX_DURATION% in Envoy docs
  • space_id: Cloud Foundry space GUID of the application
  • start_time: Request start time including milliseconds; see %START_TIME% in Envoy docs
  • upstream_cluster: Upstream cluster to which the upstream host belongs to
  • upstream_host: Upstream host URL
  • upstream_local_address: Local address of the upstream connection. If the address is an IP address it includes both address and port; see %UPSTREAM_LOCAL_ADDRESS% in Envoy docs
  • upstream_service_time: Time in milliseconds spent by the app processing the request including network latency.; see Duration Fields and these Envoy docs for more information
  • upstream_transport_failure_reason: If upstream connection failed due to a TLS failure. This field currently does not indicate any Transport Layer failures. transport socket (e.g. TLS handshake), provides the failure reason from the transport socket
  • user_agent: HTTP request User-Agent header
  • x_b3_parentspanid: Used for request tracing; see b3-propagation for more info
  • x_b3_spanid: Used for request tracing; see b3-propagation for more info
  • x_b3_traceid: Used for request tracing; see b3-propagation for more info
  • x_forwarded_for: IP of the client used to initiate the request
  • x_forwarded_proto: Protocol a client used to initiate the request. Can be http or https for HTTP traffic
Report Issues Edit