Skip to main content
Мы публикуем частые обновления нашей документации, и перевод этой страницы, возможно, еще выполняется. Актуальные сведения см. в документации на английском языке.

Поддержка этой версии GitHub Enterprise будет прекращена 2023-03-15. Исправления выпускаться не будут даже при критических проблемах безопасности. Для повышения производительности, укрепления безопасности и новых функций установите последнюю версию GitHub Enterprise. Чтобы получить справку по обновлению, обратитесь в службу поддержки GitHub Enterprise.

Доступ к панели мониторинга

GitHub Enterprise Server включает в себя веб-панель мониторинга, которая отображает исторические данные о вашем устройстве GitHub Enterprise Server, например использование ЦП и хранилища, время отклика приложения и проверки подлинности, а также общее состояние системы.

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."