Monitoring and managing your instance
You can monitor your instance, update your virtual machine resources, and configure clustering or high availability, and repository caching.
- Monitoring your instance, 1 of 7
- About monitoring your instance, 1 of 11
- About the monitor dashboards, 2 of 11
- Analyzing Git traffic on your GitHub Enterprise Server instance, 3 of 11
- Recommended alert thresholds, 4 of 11
- OpenTelemetry metrics, 5 of 11
- Collectd metrics, 6 of 11
- Monitoring using SNMP, 7 of 11
- About system logs, 8 of 11
- About support bundles for GitHub Enterprise Server, 9 of 11
- Troubleshooting resource allocation problems, 10 of 11
- Generating a Health Check for your enterprise, 11 of 11
- Updating the virtual machine and physical resources, 2 of 7
- Configuring clustering, 3 of 7
- About clustering, 1 of 13
- Differences between clustering and high availability (HA), 2 of 13
- About cluster nodes, 3 of 13
- Cluster network configuration, 4 of 13
- Initializing the cluster, 5 of 13
- Deferring database seeding, 6 of 13
- Upgrading a cluster, 7 of 13
- Monitoring the health of your cluster, 8 of 13
- Monitoring the health of your cluster nodes with Node Eligibility Service, 9 of 13
- Rebalancing cluster workloads, 10 of 13
- Replacing a cluster node, 11 of 13
- Configuring high availability replication for a cluster, 12 of 13
- Initiating a failover to your replica cluster, 13 of 13
- Configuring high availability, 4 of 7
- About high availability configuration, 1 of 9
- Configuring Elasticsearch Cross-Cluster Replication for high availability, 2 of 9
- Answers to common questions about high availability replicas, 3 of 9
- Creating a high availability replica, 4 of 9
- Monitoring a high-availability configuration, 5 of 9
- Initiating a failover to your replica appliance, 6 of 9
- Recovering a high availability configuration, 7 of 9
- Removing a high availability replica, 8 of 9
- About geo-replication, 9 of 9
- Caching repositories, 5 of 7
- Multiple data disks, 6 of 7
- Additional nodes, 7 of 7