| format |
Integer |
Yes |
The current version of the "container_usage" log entry format. |
| type |
String |
yes |
The access log entry type, which will always be "container_usage" for entries of this type.
Used for differentiation from other access log entry types such as "http", "mirror", or
"proxy." |
| timestamp_start |
long |
yes |
The timestamp, in milliseconds since epoch, when the request was initiated to the
mirror. |
| timestamp_result |
long |
yes |
The timestamp, in milliseconds since epoch, for when it was decided which vault within the
mirror to return the request's outcome from. |
| timestamp_finish |
long |
yes |
The timestamp, in milliseconds since epoch, for when it is determined that the remaining
operations to the vaults within the mirror can occur in the background. |
| time_start |
String |
yes |
A human-readable date string associated with timestamp_start (ISO 8601) |
| time_result |
String |
yes |
A human-readable date string associated with timestamp_result (ISO 8601) |
| time_finish |
String |
yes |
A human-readable date string associated with timestamp_finish (ISO 8601) |
| request_id |
String |
no |
The COS request ID, a unique identifier generate for each request to assist with event
correlation in the debug log. This request_id will match the corresponding http type access log
entry the mirror type access log entry pertains to. |
| object_name |
String |
yes |
The object's name |
| blocking_time |
Double |
yes |
The difference between the timestamp_result and timestamp_start |
| background_time |
Double |
yes |
The difference between the timestamp_finish and the timestamp result |