Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-5706

Ability to perform SQL logging for Crowd

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Support tools
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      To help with troubleshooting cases, in some Atlassian products there are a feature to capture the SQL queries that are being executed when any action is done. This feature can be enabled through the Logging and Profiling screen. 

      In Crowd however, there is no such feature in the Logging and Profiling screen and the only way to enable this by manually adding the following log parameters in the log4j.properties file

      ## Log hibernate prepared statements/SQL queries (equivalent to setting 'hibernate.show_sql' to 'true')
log4j.logger.org.hibernate.SQL=DEBUG
log4j.logger.org.hibernate.type=TRACE
log4j.appender.crowdlog.Threshold=TRACE

      The above approach means, 

      • Crowd needs to be restarted for the properties to be activated.
      • When the parameter needs to be removed, Crowd needs to be restarted again. 

            [CWD-5706] Ability to perform SQL logging for Crowd

            Denis Reidelbach added a comment -

            this feature would be great

            Denis Reidelbach added a comment - this feature would be great
            Ahmad Faridi made changes -
            Description Original: To help with troubleshooting cases, in some Atlassian products there are a feature to capture the SQL queries that are being executed when any action is done. This feature can be enabled through the *Logging and* *Profiling* screen. 

            In Crowd however, there is no such feature in the *Logging and Profiling* screen and the only way to enable this by manually adding the following log parameters in the log4j.configuration file
            {code:java}
            ## Log hibernate prepared statements/SQL queries (equivalent to setting 'hibernate.show_sql' to 'true')
            log4j.logger.org.hibernate.SQL=DEBUG
            log4j.logger.org.hibernate.type=TRACE
            log4j.appender.crowdlog.Threshold=TRACE
            {code}
             * [https://confluence.atlassian.com/crowdkb/how-to-enable-sql-logging-in-crowd-711132214.html]             		New: To help with troubleshooting cases, in some Atlassian products there are a feature to capture the SQL queries that are being executed when any action is done. This feature can be enabled through the *Logging and* *Profiling* screen. 

            In Crowd however, there is no such feature in the *Logging and Profiling* screen and the only way to enable this by manually adding the following log parameters in the log4j.properties [file|https://confluence.atlassian.com/crowdkb/how-to-enable-sql-logging-in-crowd-711132214.html]
            {code:java}
            ## Log hibernate prepared statements/SQL queries (equivalent to setting 'hibernate.show_sql' to 'true')
            log4j.logger.org.hibernate.SQL=DEBUG
            log4j.logger.org.hibernate.type=TRACE
            log4j.appender.crowdlog.Threshold=TRACE {code}
            The above approach means, 
             * Crowd needs to be restarted for the properties to be activated.
             * When the parameter needs to be removed, Crowd needs to be restarted again. 
            Ahmad Faridi created issue -

              Unassigned Unassigned
              afaridi Ahmad Faridi
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: