How to enable Envoy access logging in Rancher v2.3+ deployed Istio

This article details how to enable Envoy’s access logging, for Rancher deployed Istio, in Rancher v2.3+

Pre-requisites

To enable Access loggings for Envoy, Rancher deployed Istio by setting the global.proxy.accessLogFile path and global.proxy.accessLogEncoding type via Custom Answers on the Istio configuration.

Setting the accessLogFile path to /dev/stdout will route the Envoy access logs to the istio-sidecar container logs, exposing them via kubectl logs or any log forwarding endpoint you have configured in the cluster.

The log format, specified in accessLogEncoding, can be set to JSON or TEXT.

To enable access logging, perform the following steps:

Further reading

comments powered by Disqus