Protocol: HTTP/WebDAV Requests

This statistic shows HTTP/WebDAV requests/second requested by HTTP clients. Various useful breakdowns are available: to show the client, filename, and latency of the HTTP request.

When to Check HTTP/WebDAV Requests

HTTP/WebDAV requests/sec can be used as an indication of HTTP load, and can also be viewed on the dashboard.

Use the latency breakdown when investigating HTTP performance issues, especially to quantify the magnitude of the issue. This measures the latency component for which Oracle ZFS Storage Appliance is responsible, and displays it as a heat map so that the overall latency pattern can be seen, along with outliers. If the HTTP latency is high, drill down further on latency to identify the file, size, and response code for the high-latency HTTP requests, and check other statistics for both CPU and Disk load to investigate why Oracle ZFS Storage Appliance is slow to respond; if latency is low, the appliance is performing quickly, and any performance issues experienced on the client initiator are more likely to be caused by other factors in the environment, such as the network infrastructure, and CPU load on the client itself.

The best way to improve performance is to eliminate unnecessary work, which can be identified through the client, response code, and requested filename breakdowns.

HTTP/WebDAV Requests Breakdowns

Table 5-40 Breakdowns of HTTP/WebDAV Requests

Breakdown Description

type of operation

HTTP request type (get/post).

response code

HTTP response (200/404/...).


Client hostname or IP address.


Filename requested by HTTP.


A heat map showing the latency of HTTP requests, as measured from when the HTTP request arrived on Oracle ZFS Storage Appliance from the network, to when the response is sent; this latency includes the time to process the HTTP request, and to perform any disk I/O.


A heat map showing the distribution of HTTP request sizes.

These breakdowns can be combined to produce powerful statistics. For example:

  • Protocol: HTTP/WebDAV operations per second of type get broken down by latency (to examine latency for HTTP GETs only)

  • Protocol: HTTP/WebDAV requests per second for response code '404' broken down by filename (to see which non-existent files were requested)

  • Protocol: HTTP/WebDAV requests per second for client '' broken down by filename (to examine files requested by a particular client)

Further Analysis

See Network: Device Bytes for a measure of network throughput caused by HTTP activity. Also see Cache: ARC Accesses to learn how well an HTTP read workload is returning from cache, and Disk: I/O Operations for the back-end disk I/O caused.