Object metrics

The following section lists all the object metrics:

SwiftAccount
  • account_auditor_time: Timing data for individual account database audits.
  • account_reaper_time: Timing data for each reap_account() call.
  • account_replicator_time: Timing data for each database replication attempt not resulting in a failure.
  • account_DEL_time: Timing data for each DELETE request not resulting in an error.
  • account_DEL_err_time: Timing data for each DELETE request resulting in an error: bad request, not mounted, missing timestamp.
  • account_GET_time: Timing data for each GET request not resulting in an error.
  • account_GET_err_time: Timing data for each GET request resulting in an error: bad request, not mounted, bad delimiter, account listing limit too high, bad accept header.
  • account_HEAD_time: Timing data for each HEAD request not resulting in an error.
  • account_HEAD_err_time: Timing data for each HEAD request resulting in an error: bad request, not mounted.
  • account_POST_time: Timing data for each POST request not resulting in an error.
  • account_POST_err_time: Timing data for each POST request resulting in an error: bad request, bad or missing timestamp, not mounted.
  • account_PUT_time: Timing data for each PUT request not resulting in an error.
  • account_PUT_err_time: Timing data for each PUT request resulting in an error: bad request, not mounted, conflict, recently-deleted.
  • account_REPLICATE_time: Timing data for each REPLICATE request not resulting in an error.
  • account_REPLICATE_err_time: Timing data for each REPLICATE request resulting in an error: bad request, not mounted.
SwiftContainer
  • container_auditor_time: Timing data for each container audit.
  • container_replicator_time: Timing data for each database replication attempt not resulting in a failure.
  • container_DEL_time: Timing data for each DELETE request not resulting in an error.
  • container_DEL_err_time: Timing data for DELETE request errors: bad request, not mounted, missing timestamp, conflict.
  • container_GET_time: Timing data for each GET request not resulting in an error.
  • container_GET_err_time: Timing data for GET request errors: bad request, not mounted, parameters not utf8, bad accept header.
  • container_HEAD_time: Timing data for each HEAD request not resulting in an error.
  • container_HEAD_err_time: Timing data for HEAD request errors: bad request, not mounted.
  • container_POST_time: Timing data for each POST request not resulting in an error.
  • container_POST_err_time: Timing data for POST request errors: bad request, bad x-container-sync-to, not mounted.
  • container_PUT_time: Timing data for each PUT request not resulting in an error.
  • container_PUT_err_time: Timing data for PUT request errors: bad request, missing timestamp, not mounted, conflict.
  • container_REPLICATE_time: Timing data for each REPLICATE request not resulting in an error.
  • container_REPLICATE_err_time: Timing data for REPLICATE request errors: bad request, not mounted.
  • container_sync_deletes_time: Timing data for each container database row synchronization via deletion.
  • container_sync_puts_time: Timing data for each container database row synchronization via PUTing.
  • container_updater_time: Timing data for processing a container; only includes timing for containers which needed to update their accounts.
SwiftObject
  • object_auditor_time: Timing data for each object audit (does not include any rate-limiting sleep time for max_files_per_second, but does include rate-limiting sleep time for max_bytes_per_second).
  • object_expirer_time: Timing data for each object expiration attempt, including ones resulting in an error.
  • object_replicator_partition_delete_time: Timing data for partitions replicated to another node because they didn’t belong on this node. This metric is not tracked per device.
  • object_replicator_partition_update_time: Timing data for partitions replicated which also belong on this node. This metric is not tracked per-device.
  • object_DEL_time: Timing data for each DELETE request not resulting in an error.
  • object_DEL_err_time: Timing data for DELETE request errors: bad request, missing timestamp, not mounted, precondition failed. Includes requests which couldn’t find or match the object.
  • object_GET_time: Timing data for each GET request not resulting in an error. Includes requests which couldn’t find the object (including disk errors resulting in file quarantine).
  • object_GET_err_time: Timing data for GET request errors: bad request, not mounted, header timestamps before the epoch, precondition failed. File errors resulting in a quarantine are not counted here.
  • object_HEAD_time: Timing data for each HEAD request not resulting in an error. Includes requests which couldn’t find the object (including disk errors resulting in file quarantine).
  • object_HEAD_err_time: Timing data for HEAD request errors: bad request, not mounted.
  • object_POST_time: Timing data for each POST request not resulting in an error.
  • object_POST_err_time: Timing data for POST request errors: bad request, missing timestamp, delete-at in past, not mounted.
  • object_PUT_time: Timing data for each PUT request not resulting in an error.
  • object_PUT_err_time: Timing data for PUT request errors: bad request, not mounted, missing timestamp, object creation constraint violation, delete-at in past.
  • object_REPLICATE_time: Timing data for each REPLICATE request not resulting in an error.
  • object_REPLICATE_err_time: Timing data for REPLICATE request errors: bad request, not mounted.
  • object_updater_time: Timing data for object sweeps to flush async_pending container updates. Does not include object sweeps which did not find an existing async_pending storage directory.
SwiftProxy
  • proxy_account_latency: Timing data up to completion of sending the response headers, 200: standard response for successful HTTP requests.
  • proxy_container_latency: Timing data up to completion of sending the response headers, 200: standard response for successful HTTP requests.
  • proxy_object_latency: Timing data up to completion of sending the response headers, 200: standard response for successful HTTP requests.
  • proxy_account_GET_time: Timing data for GET request, start to finish, 200: standard response for successful HTTP requests
  • proxy_account_GET_bytes: The sum of bytes transferred in (from clients) and out (to clients) for requests, 200: standard response for successful HTTP requests.
  • proxy_account_HEAD_time: Timing data for HEAD request, start to finish, 204: request processed, no content returned.
  • proxy_account_HEAD_bytes: The sum of bytes transferred in (from clients) and out (to clients) for requests, 204: request processed, no content returned.
  • proxy_container_DEL_time: Timing data for DELETE request, start to finish, 204: request processed, no content returned.
  • proxy_container_DEL_bytes: The sum of bytes transferred in (from clients) and out (to clients) for requests, 204: request processed, no content returned.
  • proxy_container_GET_time: Timing data for GET request, start to finish, 200: standard response for successful HTTP requests.
  • proxy_container_GET_bytes: The sum of bytes transferred in (from clients) and out (to clients) for requests, 200: standard response for successful HTTP requests.
  • proxy_container_HEAD_time: Timing data for HEAD request, start to finish, 204: request processed, no content returned.
  • proxy_container_HEAD_bytes: The sum of bytes transferred in (from clients) and out (to clients) for requests, 204: request processed, no content returned. 1
  • proxy_container_PUT_time: Timing data for each PUT request not resulting in an error, 201: request has been fulfilled; new resource created.
  • proxy_container_PUT_bytes: The sum of bytes transferred in (from clients) and out (to clients) for requests, 201: request has been fulfilled; new resource created.
  • proxy_object_DEL_time: Timing data for DELETE request, start to finish, 204: request processed, no content returned.
  • proxy_object_DEL_bytes: The sum of bytes transferred in (from clients) and out (to clients) for requests, 204: request processed, no content returned.
  • proxy_object_GET_time: Timing data for GET request, start to finish, 200: standard response for successful HTTP requests.
  • proxy_object_GET_bytes: The sum of bytes transferred in (from clients) and out (to clients) for requests, 200: standard response for successful HTTP requests.
  • proxy_object_HEAD_time: Timing data for HEAD request, start to finish, 200: request processed, no content returned.
  • proxy_object_HEAD_bytes: The sum of bytes transferred in (from clients) and out (to clients) for requests, , 200: request processed, no content returned.
  • proxy_object_PUT_time: Timing data for each PUT request not resulting in an error, 201: request has been fulfilled; new resource created.
  • proxy_object_PUT_bytes: The sum of bytes transferred in (from clients) and out (to clients) for requests, 201: request has been fulfilled; new resource created.
Note: For information about computed metrics for object, see Performance monitoring for object metrics.
Parent topic: Protocol metrics