About the benefits of Server Statistics
Server Statistics can help you anticipate the needs of your organization, understand how your team works, and show the value you get from GitHub Enterprise Server.
Once enabled, Server Statistics collects aggregate data on how much certain features are used on your instance over time. Unlike other Admin Stats API endpoints, which only return data for the last day, Server Statistics provides historical data of all Server Statistics metrics collected since the day you enabled the feature. For more information, see "Enabling Server Statistics for your enterprise."
When you enable Server Statistics, you're helping to build a better GitHub. The aggregated data you'll provide gives us insights into how GitHub adds value to our customers. This information allows GitHub to make better and more informed product decisions, ultimately benefiting you.
About data security
We respect your data. We will never transmit data from your GitHub Enterprise Server instance unless you have first given us permission to do so.
We collect no personal data. We also don't collect any GitHub content, such as code, issues, comments, or pull request content.
Only owners of the connected enterprise account or organization on GitHub Enterprise Cloud can access the data.
Only certain aggregate metrics are collected on repositories, issues, pull requests, and other features. To see the list of aggregate metrics collected, see "Server Statistics data collected."
Any updates to the collected metrics will happen in future feature releases of GitHub Enterprise Server and will be described in the GitHub Enterprise Server release notes. In addition, we will update this article with all metric updates.
For a better understanding of how we store and secure Server Statistics data, see "GitHub Security."
About data retention and deletion
GitHub collects Server Statistics data for as long as your GitHub Enterprise Server license is active and the Server Statistics feature is enabled.
If you would like to delete your data, you may do so by contacting GitHub Support, your GitHub account representative, or your Customer Success Manager. Generally, we delete data in the timeframe specified in our privacy statement. For more information, see GitHub's privacy statement in the GitHub.com documentation.
About data portability
As an organization owner or enterprise owner on GitHub Enterprise Cloud, you can access Server Statistics data by exporting the data in a CSV or JSON file or through the Server Statistics REST API. For more information, see "Requesting Server Statistics using the REST API" or "Exporting Server Statistics."
About disabling data collection
You can disable the Server Statistics feature at any time. For more information, see "Enabling Server Statistics for your enterprise."
Server Statistics data collected
After you enable Server Statistics, metrics are collected through a daily job that runs on your GitHub Enterprise Server instance. The aggregate metrics are stored on your organization or enterprise account on GitHub Enterprise Cloud and are not stored on your GitHub Enterprise Server instance.
The following aggregate metrics will be collected and transmitted on a daily basis and represent the total counts for the day.
|A||Array of GitHub Connect features that are enabled for your instance (see "About GitHub Connect" )|
|B||The hostname for your instance|
|C||The length of time a user must be inactive to be considered dormant|
|D||Number of dormant user accounts|
|E||The version of GitHub Enterprise Server that your instance is running|
|F||The UUID generated for your instance|
|G||The date the metrics were collected|
|H||The version of the database schema used to store this data|
|I||Number of comments on commits|
|J||Number of comments on gists|
|K||Number of comments on issues|
|L||Number of comments on pull requests|
|M||Number of gists (both secret and public)|
|N||Number of secret gists|
|O||Number of public gists|
|P||Number of pre-receive hooks (both active and inactive)|
|Q||Number of active pre-receive hooks|
|R||Number of inactive pre-receive hooks|
|S||Number of issues (both open and closed)|
|T||Number of open issues|
|U||Number of closed issues|
|V||Number of milestones (both open and closed)|
|W||Number of open milestones|
|X||Number of closed milestones|
|Y||Number of organizations (both enabled and disabled)|
|Z||Number of disabled organizations|
|AA||Number of teams|
|AB||Number of team members|
|AC||Number of GitHub Pages sites|
|AD||Number of pull requests|
|AE||Number of merged pull requests|
|AF||Number of pull requests that are currently mergeable|
|AG||Number of pull requests that are currently unmergeable|
|AH||Number of repositories (both upstream repositories and forks)|
|AI||Number of upstream repositories|
|AJ||Number of forks|
|AK||Number of repositories owned by organizations|
|AL||Number of pushes to repositories|
|AM||Number of wikis|
|AN||Number of user accounts|
|AO||Number of user accounts that are site administrators|
|AP||Number of user accounts that are suspended|
Server Statistics data examples
To see an example of the headings included in the CSV export for Server Statistics, download the Server Statistics CSV example.
To see an example of the response payload for the Server Statistics API, see "Requesting Server Statistics using the REST API."