custom proxy_access_log still not working in 3.4.* about kong HOT 5 CLOSED

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 :)

from kong.

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.

from kong.

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

from kong.

Dear contributor,

We are automatically closing this issue because it has not seen any activity for three weeks.
We're sorry that your issue could not be resolved. If any new information comes up that could
help resolving it, please feel free to reopen it.

Your contribution is greatly appreciated!

Please have a look
our pledge to the community
for more information.

Sincerely,
Your Kong Gateway team

from kong.

Thanks and Sorry for the delayed reply @samugi. I was holidaying and just came back. I have setup my environment variable such a way (KONG_PROXY_ACCESS_LOG=/dev/stdout\ customer-json) because my custom-json.conf file defines log_format as customer-json (According to the documentation, I believe we need to set the log_format attribute name, not the file name). I will attempt to recreate this issue in a small project and provide a GitHub link for you to review. It will help to determine if I am doing something differently from your setup.

from kong.