Queries regarding Reports available on site admin dashboard

I have a few questions regarding the all_users.csv report available in the Site Admin dashboard:
1- What is the criteria for defining a user dormant?
2- Is there any time lag between the activity performed and the last active date updated in the report? If yes, then how much?
3- Which all activities qualify for updating the last activity date of the user?
4- is this report available only for the GitHub Enterprise on Premise or is it also available for github.com?

:wave: @himankgupta81 , thanks for raising these questions!

1- What is the criteria for defining a user dormant?

For GitHub Enterprise Server 2.22, a user account is considered to be inactive (“dormant”) when it:

  • Has existed for longer than the dormancy threshold that’s set for your GitHub Enterprise Server instance.
  • Has not generated any activity within that time period.
  • Is not a site administrator.

Our team wrote more about the dormancy threshold in the Dormant users section, in addition to configuring that threshold in this guide.

If you’re using a different GitHub Enterprise Server version than 2.22, there’s a dropdown showcasing all the other supported versions that you can view the content in:

4- is this report available only for the GitHub Enterprise on Premise or is it also available for github.com ?

This report is available only for GitHub Enterprise Server (also known as GitHub Enterprise On Premise).


2- Is there any time lag between the activity performed and the last active date updated in the report? If yes, then how much?

3- Which all activities qualify for updating the last activity date of the user?

I’ve asked my colleagues for an assist on these two questions and will write back as soon as I have an update. :+1:

:wave: @himankgupta81, I have an update! :smile_cat:

2- Is there any time lag between the activity performed and the last active date updated in the report? If yes, then how much?

I spoke with one of my colleagues and they shared their input with me:

When a GitHub Enterprise Server site administrator requests the All Users Stafftools report, a background job is started to generate the report based on information contained in the GitHub Enterprise Server database. Once the background job completes the report is available for download. The time it takes for the Stafftools report background job to run may vary depending on the current load and performance of your GitHub Enterprise Server, although on non-busy instances we’d usually expect the job to completed within several minutes.

For a performant GitHub Enterprise Server instance, there shouldn’t be any delay between actions the user performs and the user’s last_active date as reflected in the Stafftools reports.


You also asked:

3- Which all activities qualify for updating the last activity date of the user?

Here’s a list of actions that will update the last_active field:

  • active sessions: An active session is a day that the person has visited the site while logged in. Excludes people who have visited the same day they signed up.
  • web edits: A web edit is using the web UI to create a branch, tag, or do a file
    create, edit, delete operation.
  • pull requests: Submitting a new pull request
  • issues: Submitting a new issue.
  • comments: Commenting on an a Commit, an Issue, a Pull Request, and Pull Request Review Comments.
  • pushes: Git Pushes.
  • wiki edits: Creating, editing, and deleting a wiki page.
  • releases: Creating a new Release

We hope this helps!