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.
All products
Enterprise administrators

This version of GitHub Enterprise was discontinued on 2023-03-15. 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.

Monitoring your appliance

As use of your GitHub Enterprise Server instance increases over time, the utilization of system resources, like CPU, memory, and storage will also increase. You can configure monitoring and alerting so that you're aware of potential issues before they become critical enough to negatively impact application performance or availability.

  • Accessing the monitor dashboard

    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.

  • Recommended alert thresholds

    You can configure an alert to notify you of system resource issues before they affect your GitHub Enterprise Server appliance's performance.

  • Setting up external monitoring

    You can monitor basic system resources on your GitHub Enterprise Server appliance using either the SNMP or collectd statistics collection protocols.

  • Configuring collectd

    GitHub Enterprise can gather data with collectd and send it to an external collectd server. Among other metrics, we gather a standard set of data such as CPU utilization, memory and disk consumption, network interface traffic and errors, and the VM's overall load.

  • Monitoring using SNMP

    GitHub Enterprise provides data on disk usage, CPU utilization, memory usage, and more over SNMP.

  • About system logs

    GitHub Enterprise Server keeps error and message logs for system events. Logs are useful for identifying user, application and system-level actions and exceptions.

  • Generating a Health Check for your enterprise

    You can gain insight into the general health and Git and API requests of your GitHub Enterprise Server instance by generating a Health Check.