Hello Mark, @mark-robustelli
The post is rather vague indeed.

My question is about FusionAuth configuration using helm charts :

• What env variable should I specify in order to get DEBUG logging instead of the INFO level by default?

containers:
       - name: fusionauth
         image: fusionauth/fusionauth-app:1.55.1
         ports:
           - name: http
             containerPort: 9011
             protocol: TCP
         env:
         # REDACTED
           - name: SEARCH_TYPE
             value: database
           - name: FUSIONAUTH_APP_MEMORY
             value: 256M
           - name: FUSIONAUTH_APP_RUNTIME_MODE
             value: development
           - name: FUSIONAUTH_APP_SILENT_MODE
             value: 'false'
           # question: what env var should I put here in order to get DEBUG logging instead of the INFO level by default?

regards,
Max.

@mark-robustelli
Hello,
The doc only mentions : "Minimal tracing capability unless debug logging is enabled. Logs are also written to the Docker standard output (terminal)."

I can see the Docker standard output, my question is how to change the log level from INFO (default) to DEBUG (or even TRACE) in order to see more details system logs.

Re: Is it possible to enable debug logging on FusionAuth?

Could you please document how to enable more logs on FusionAuth (containerized version) ?
More specifically, what value should I put inside FUSIONAUTH_ADDITIONAL_JAVA_ARGS ?

Thanks in advance for your help.
Maxime.