Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-58875

Add logging to export the list of licensed Confluence users

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently it is difficult to find out which users are taking up a license. It would be great to be able to see this. A quick way to do it would be to provide a log level that displays the list of users.

      After this is implemented users will need to follow the following steps to see the list of licensed users:

      1. Go to the "Logging and profiling" administration screen
      2. Add an entry for "com.atlassian.confluence.user.DefaultUserAccessor" with level "DEBUG"
      3. Go to the "License Details" administration screen
      4. Tail your Confluence log file
      5. Hit the "Refresh" button under the "Licensed users" section
      6. Look for a line like this in your log file
      2019-09-17 10:36:34,271 DEBUG [read-only-transaction:thread-1] [atlassian.confluence.user.DefaultUserAccessor] getUserNamesWithConfluenceAccess Found n licensed users: [user1, user2, ...] 

          Form Name

            [CONFSERVER-58875] Add logging to export the list of licensed Confluence users

            Hello nbhawnani,
            Thanks for the confirmation. I'm surprised about the tone of your answer ("it should"... ). I was in the idea that you are now doing scaling test for any new features before to deliver it. Seems I was wrong.

            I won't jeopardize my production instance (and my 14.000 users) by doing the test by myself 

            Cheer,
            Phil.

             

            Philippe PEREZ added a comment - Hello  nbhawnani , Thanks for the confirmation. I'm surprised about the tone of your answer ("it should"... ). I was in the idea that you are now doing scaling test for any new features before to deliver it. Seems I was wrong. I won't jeopardize my production instance (and my 14.000 users) by doing the test by myself  Cheer, Phil.  

            Hi philippe.perez. You can refer to our documentation on the subject for more information. With 14,000 users it should still work fine but obviously will take a little longer. We still intend to eventually provide a proper way (in UI) to do this but for now this is the best option.

            Regards,
            Niraj Bhawnani
            Engineering Manager, Confluence Server
            Atlassian

            Niraj Bhawnani added a comment - Hi philippe.perez . You can refer to our documentation on the subject for more information. With 14,000 users it should still work fine but obviously will take a little longer. We still intend to eventually provide a proper way (in UI) to do this but for now this is the best option. Regards, Niraj Bhawnani Engineering Manager, Confluence Server Atlassian

            Hello,

            Can you explain how this fix was implemented ? 
            Is it per the process suggested ? Else how this list of users can be retrieved ? How is it dealing with 14.000 users to list ?

            Thanks.

             

             

            Philippe PEREZ added a comment - Hello, Can you explain how this fix was implemented ?  Is it per the process suggested ? Else how this list of users can be retrieved ? How is it dealing with 14.000 users to list ? Thanks.    

            Quan Pham added a comment -

            A fix for this issue is available to Server and Data Center customers in Confluence 6.15.10
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            Quan Pham added a comment - A fix for this issue is available to Server and Data Center customers in Confluence 6.15.10 Upgrade now or check out the Release Notes to see what other issues are resolved.

            If you're running the Confluence 6.13 Enterprise release, a fix for this issue is now available in Confluence 6.13.9, which you can find in the Download Archives.

            Bradley Hyde added a comment - If you're running the Confluence 6.13 Enterprise release, a fix for this issue is now available in Confluence 6.13.9, which you can find in the Download Archives .

            Zac Xu added a comment -

            If you're running the Confluence 6.6 Enterprise release, a fix for this issue is now available in Confluence 6.6.17, which you can find in the Download Archives.

            Zac Xu added a comment - If you're running the Confluence 6.6 Enterprise release, a fix for this issue is now available in Confluence 6.6.17, which you can find in the Download Archives .

            Zac Xu added a comment -

            A fix for this issue is available to Server and Data Center customers in Confluence 7.1.0
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            Zac Xu added a comment - A fix for this issue is available to Server and Data Center customers in Confluence 7.1.0 Upgrade now or check out the Release Notes to see what other issues are resolved.

            Zac Xu added a comment -

            A fix for this issue is available to Server and Data Center customers in Confluence 7.0.2.

            Upgrade now or check out the Confluence 7.0.2 Release Notes to see what other issues are resolved.

            Zac Xu added a comment - A fix for this issue is available to Server and Data Center customers in Confluence 7.0.2. Upgrade now or check out the Confluence 7.0.2 Release Notes to see what other issues are resolved.

              nbhawnani Niraj Bhawnani
              nbhawnani Niraj Bhawnani
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: