Pilot Discovery logs filling with the value for accessLogFormat

We are running 1.3.4 and we recently noticed that our Pilot’s discovery container logs are filling up with the same message over and over and it is a map which essentially just contains the value we have configured for the accessLogFormat in the istio configmap. Below is a snippet of that. Has anyone else seen this and more importantly, any way to disable this. I am curious why it is only interested in that one property.

map[authority:%REQ(:AUTHORITY)% bytes_send:%BYTES_SENT% downstream_local_address:%DOWNSTREAM_LOCAL_ADDRESS% downstream_remote_address:%DOWNSTREAM_REMOTE_ADDRESS% duration:%DURATION% path:%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% protocol:%PROTOCOL% req_method:%REQ(:METHOD)% resp_x_envoy_upstream_service_time:%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)% response_code:%RESPONSE_CODE% start_time:%START_TIME% upstream_cluster:%UPSTREAM_CLUSTER% upstream_host:%UPSTREAM_HOST% upstream_transport_failure_reason:%UPSTREAM_TRANSPORT_FAILURE_REASON% user_agent:%REQ(USER-AGENT)% x_client_id:%REQ(X-CLIENT-ID)% x_forwarded_for:%REQ(X-FORWARDED-FOR)% x_request_id:%REQ(X-REQUEST-ID)%]
map[authority:%REQ(:AUTHORITY)% bytes_send:%BYTES_SENT% downstream_local_address:%DOWNSTREAM_LOCAL_ADDRESS% downstream_remote_address:%DOWNSTREAM_REMOTE_ADDRESS% duration:%DURATION% path:%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% protocol:%PROTOCOL% req_method:%REQ(:METHOD)% resp_x_envoy_upstream_service_time:%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)% response_code:%RESPONSE_CODE% start_time:%START_TIME% upstream_cluster:%UPSTREAM_CLUSTER% upstream_host:%UPSTREAM_HOST% upstream_transport_failure_reason:%UPSTREAM_TRANSPORT_FAILURE_REASON% user_agent:%REQ(USER-AGENT)% x_client_id:%REQ(X-CLIENT-ID)% x_forwarded_for:%REQ(X-FORWARDED-FOR)% x_request_id:%REQ(X-REQUEST-ID)%]
map[authority:%REQ(:AUTHORITY)% bytes_send:%BYTES_SENT% downstream_local_address:%DOWNSTREAM_LOCAL_ADDRESS% downstream_remote_address:%DOWNSTREAM_REMOTE_ADDRESS% duration:%DURATION% path:%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% protocol:%PROTOCOL% req_method:%REQ(:METHOD)% resp_x_envoy_upstream_service_time:%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)% response_code:%RESPONSE_CODE% start_time:%START_TIME% upstream_cluster:%UPSTREAM_CLUSTER% upstream_host:%UPSTREAM_HOST% upstream_transport_failure_reason:%UPSTREAM_TRANSPORT_FAILURE_REASON% user_agent:%REQ(USER-AGENT)% x_client_id:%REQ(X-CLIENT-ID)% x_forwarded_for:%REQ(X-FORWARDED-FOR)% x_request_id:%REQ(X-REQUEST-ID)%]
map[authority:%REQ(:AUTHORITY)% bytes_send:%BYTES_SENT% downstream_local_address:%DOWNSTREAM_LOCAL_ADDRESS% downstream_remote_address:%DOWNSTREAM_REMOTE_ADDRESS% duration:%DURATION% path:%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% protocol:%PROTOCOL% req_method:%REQ(:METHOD)% resp_x_envoy_upstream_service_time:%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)% response_code:%RESPONSE_CODE% start_time:%START_TIME% upstream_cluster:%UPSTREAM_CLUSTER% upstream_host:%UPSTREAM_HOST% upstream_transport_failure_reason:%UPSTREAM_TRANSPORT_FAILURE_REASON% user_agent:%REQ(USER-AGENT)% x_client_id:%REQ(X-CLIENT-ID)% x_forwarded_for:%REQ(X-FORWARDED-FOR)% x_request_id:%REQ(X-REQUEST-ID)%]
map[authority:%REQ(:AUTHORITY)% bytes_send:%BYTES_SENT% downstream_local_address:%DOWNSTREAM_LOCAL_ADDRESS% downstream_remote_address:%DOWNSTREAM_REMOTE_ADDRESS% duration:%DURATION% path:%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% protocol:%PROTOCOL% req_method:%REQ(:METHOD)% resp_x_envoy_upstream_service_time:%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)% response_code:%RESPONSE_CODE% start_time:%START_TIME% upstream_cluster:%UPSTREAM_CLUSTER% upstream_host:%UPSTREAM_HOST% upstream_transport_failure_reason:%UPSTREAM_TRANSPORT_FAILURE_REASON% user_agent:%REQ(USER-AGENT)% x_client_id:%REQ(X-CLIENT-ID)% x_forwarded_for:%REQ(X-FORWARDED-FOR)% x_request_id:%REQ(X-REQUEST-ID)%]
map[authority:%REQ(:AUTHORITY)% bytes_send:%BYTES_SENT% downstream_local_address:%DOWNSTREAM_LOCAL_ADDRESS% downstream_remote_address:%DOWNSTREAM_REMOTE_ADDRESS% duration:%DURATION% path:%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% protocol:%PROTOCOL% req_method:%REQ(:METHOD)% resp_x_envoy_upstream_service_time:%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)% response_code:%RESPONSE_CODE% start_time:%START_TIME% upstream_cluster:%UPSTREAM_CLUSTER% upstream_host:%UPSTREAM_HOST% upstream_transport_failure_reason:%UPSTREAM_TRANSPORT_FAILURE_REASON% user_agent:%REQ(USER-AGENT)% x_client_id:%REQ(X-CLIENT-ID)% x_forwarded_for:%REQ(X-FORWARDED-FOR)% x_request_id:%REQ(X-REQUEST-ID)%]

The other thing I forgot to mention is that this extra logging only seems to occur when the acessLogEncoding is JSON, AND you define a custom accessLogFormat.