One of the most commonly requested, important, and utilized metric, this graph helps measure current or hypothetical user satisfaction. It can easily convey if performance goals are being met for each page or transaction and can capture the increase or decrease in response times in relation to other load activities.

This metric can be either detailed or generalized. If the data points to an issue, the metric is given in a more detailed manner by associating utilization and response times with number of users or transactions. In this way, the requirement threshold can be seen visually and understood as it relates to the current usage or potential growth of the system. Resources reported on include processor, memory, disk I/O, and network I/O.

Very useful to the technical team, the component response times helps determine what parts are responsible for the end-user response times. If applicable, the metric ties the component response times to end-user actions to help understand the relationship.

Extremely useful for systems with frequent builds, this chart show performance improvements or degradations over time and can pinpoint exact code or application changes that cause performance issues, or improved performance.

Metrics related to these include hits per second, transactions per second, bandwidth usage, and database storage. When put in context with other metrics, these can help point to areas with current or impending performance issues.