Skip to main content

This version of GitHub Enterprise Server was discontinued on 2024-03-26. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise Server. For help with the upgrade, contact GitHub Enterprise support.

Including data about GitHub Actions in Server Statistics

You can help us improve GitHub Actions by allowing Server Statistics to collect data about GitHub Actions.

Who can use this feature?

Enterprise owners can include data about GitHub Actions in Server Statistics.

Note: Including GitHub Actions data in Server Statistics is in public beta and subject to change.

Data collected

If you enable the collection of data about GitHub Actions, the following data will be collected for your GitHub Enterprise Server instance.

  • The top 20 actions used per month, by organization
  • Number of checks run, by organization
  • Number of jobs per hour, day, week, and month, by organization
  • Maximum concurrency of running jobs, by organization and operating system
  • Workflows per operating system, by organization
  • Job run length, by organization
  • Number of job runners, by type (no names or IP addresses are collected)
  • Job distribution over types of runners

Enabling the collection of data about GitHub Actions

  1. SSH into your GitHub Enterprise Server instance. If your instance comprises multiple nodes, for example if high availability or geo-replication are configured, SSH into the primary node. If you use a cluster, you can SSH into any node. Replace HOSTNAME with the hostname for your instance, or the hostname or IP address of a node. For more information, see "Accessing the administrative shell (SSH)."

    ssh -p 122 admin@HOSTNAME
  2. Enter the following command.

    ghe-config app.github.enable-actions-usage-stats true
  3. To apply the configuration, run the following command.

    Note: During a configuration run, services on your GitHub Enterprise Server instance may restart, which can cause brief downtime for users.

  4. Wait for the configuration run to complete.