container-server Metrics¶
Note
“Not Found” is not considered an error and requests
which increment errors are not included in the timing data.
| Metric Name | Description | 
| 
 | Timing data for DELETE request errors: bad request, not mounted, missing timestamp, conflict. | 
| 
 | Timing data for each DELETE request not resulting in an error. | 
| 
 | Timing data for PUT request errors: bad request, missing timestamp, not mounted, conflict. | 
| 
 | Timing data for each PUT request not resulting in an error. | 
| 
 | Timing data for HEAD request errors: bad request, not mounted. | 
| 
 | Timing data for each HEAD request not resulting in an error. | 
| 
 | Timing data for GET request errors: bad request, not mounted, parameters not utf8, bad accept header. | 
| 
 | Timing data for each GET request not resulting in an error. | 
| 
 | Timing data for REPLICATE request errors: bad request, not mounted. | 
| 
 | Timing data for each REPLICATE request not resulting in an error. | 
| 
 | Timing data for POST request errors: bad request, bad x-container-sync-to, not mounted. | 
| 
 | Timing data for each POST request not resulting in an error. | 
