Disk usage (Root Device)

Growth on this volume is generally due to logging, which is on a 24 hour rotation schedule.

The root volume reaching 100% usage can cause a system outage, or indicate a service issue which is causing extreme log growth.

Disk usage (Data Device dm-0)

Disk space in bytes available for the user data volume.

All user profile data, pull request and issue metadata, repositories, and release assets are stored on this device.

The data volume reaching 85% usage will cause problems with the built in search functionality of GitHub Enterprise. It is recommended toincrease storage capacityof the data volume prior to reaching 85% usage.

Disk latency (Root Device & Data Device dm-0)

For best IO performance, average latency values below 10ms are recommended.

Large spikes may be an indication of storage system saturation.

Disk operations (Root Device)

Abnormally large amounts of time spent in root IO suddenly appearing may indicate a logging issue, or a general storage problem.

Disk operations (Data Device dm-0)

Abnormally large amounts of time spent in data volume IO suddenly appearing may indicate a repository maintenance issue, or a general storage problem.

Graph for reads trends generally follows the pattern of Git fetch or clone traffic on the system.

Disk pending operations (root Device)

Pending disk operations on the root device may indicate storage system saturation for the root volume.

Disk pending operations (Data Device dm-0)

Pending disk operations on the data device may indicate storage system saturation for the data volume.

Disk traffic (Root Device)

Write traffic on the root volume is mostly due to logging andcollectdgraph data collection.

Read traffic on the root volume is typically very low; However, support bundle generation may cause temporary spikes.

Disk traffic (Data Device dm-0)

Read and write trends depend on user and integration activity.

Plateaus in this graph may indicate storage system saturation.

Continue the conversation

There's more to come in the "Understanding your graphs" mini-series. If you'd like to follow along, just subscribe to the "Understanding your graphs" label (link below). Please let us know if you have any questions in the comments.