FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login

    how to enable DEBUG or TRACE logging on FusionAuth

    Scheduled Pinned Locked Moved Unsolved
    Q&A
    2
    6
    585
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      dev
      last edited by

      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.

      mark.robustelliM 1 Reply Last reply Reply Quote 0
      • mark.robustelliM
        mark.robustelli @dev
        last edited by

        @dev Here is some information on monitoring FusionAuth. Is this the information you are looking for?

        D 1 Reply Last reply Reply Quote 0
        • D
          dev @mark.robustelli
          last edited by

          @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.

          mark.robustelliM 1 Reply Last reply Reply Quote 0
          • mark.robustelliM
            mark.robustelli @dev
            last edited by

            @dev I was able to find this post about the ADDITIONAL_JAVA_ARGS and logging, but it doesn't seem to be a great answer. Can you tell me a little more specifically about what kind of information you are after? Maybe there is another way to it.

            D 1 Reply Last reply Reply Quote 0
            • D
              dev @mark.robustelli
              last edited by

              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.robustelliM 1 Reply Last reply Reply Quote 0
              • mark.robustelliM
                mark.robustelli @dev
                last edited by

                @dev I am not sure you can set that level of debugging in FusionAuth. You can change logging in the AdminUI for various things like Lambdas, CORS filter, and that sort of thing.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post