Skip to main content
We publish frequent updates to our documentation, and translation of this page may still be in progress. For the most current information, please visit the English documentation.
� 

� 

This version of GitHub Enterprise was discontinued on 2023-01-18. 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. For help with the upgrade, contact GitHub Enterprise support.

Accessing the monitor dashboard

In this article

GitHub Enterprise Server includes a web-based monitoring dashboard that displays historical data about your GitHub Enterprise Server appliance, such as CPU and storage usage, application and authentication response times, and general system health.

Accessing the monitor dashboard

  1. From an administrative account on GitHub Enterprise Server, in the upper-right corner of any page, click .

    Screenshot of the rocket ship icon for accessing site admin settings

  2. If you're not already on the "Site admin" page, in the upper-left corner, click Site admin.

    Screenshot of "Site admin" link

  3. In the left sidebar, click Management Console. Management Console tab in the left sidebar

  4. At the top of the page, click Monitor. The Monitor Dashboard link

Troubleshooting common resource allocation problems on your appliance

Note: Because regularly polling your GitHub Enterprise Server instance with continuous integration (CI) or build servers can effectively cause a denial of service attack that results in problems, we recommend using webhooks to push updates. For more information, see "About webhooks".

Use the monitor dashboard to stay informed on your appliance's resource health and make decisions on how to fix high usage issues.

ProblemPossible cause(s)Recommendations
High CPU usageVM contention from other services or programs running on the same hostIf possible, reconfigure other services or programs to use fewer CPU resources. To increase total CPU resources for the VM, see "Increasing CPU or memory resources."
High memory usageVM contention from other services or programs running on the same hostIf possible, reconfigure other services or programs to use less memory. To increase the total memory available on the VM, see "Increasing CPU or memory resources."
Low disk space availabilityLarge binaries or log files consuming disk spaceIf possible, host large binaries on a separate server, and compress or archive log files. If necessary, increase disk space on the VM by following the steps for your platform in "Increasing storage capacity."
Higher than usual response timesOften caused by one of the above issuesIdentify and fix the underlying issues. If response times remain high, contact GitHub Enterprise Support.
Elevated error ratesSoftware issuesContact GitHub Enterprise Support and include your support bundle. For more information, see "Providing data to GitHub Enterprise Support."