custom proxy_access_log still not working in 3.4.* about kong

[ravigunasekara]

I am sharing the workaround I have implemented in case others experience the same issues.
I have modified Dockerfile in a way that it override the current access_log in nginx-kong.conf file that it uses my own log formatter(customer-json).
Added below line to Dockerfile

RUN set -xe && \
    kong prepare -p "${KONG_PATH}" && \
		sed -i "s|access_log /dev/stdout kong_log_format|access_log /dev/stdout customer-json|" ${KONG_PATH}/nginx-kong.conf && \
    true	

Hope this helps :)

[samugi]

Hi @ravigunasekara, thank you for opening this issue.

I couldn't reproduce it in 3.4.3.6, I noticed, however, that you have defined a custom format named custom-json and then configured a slightly different name in your environment variable: KONG_PROXY_ACCESS_LOG=/dev/stdout\ customer-json, i.e. customer instead of custom. Could that be the problem?

Thank you.

[github-actions]

This issue is marked as stale because it has been open for 14 days with no activity.