Expiration access log entry

Edit online

These fields are common to both Container Expiration Access Log and Vault Expiration Access Log.

Table 1. Container Expiration Access Log and Vault Expiration Access log entry fields
Field name Type Required Description
format Integer yes The current version of the "lifecycle" log entry format
type String yes The access log entry type, which will always be "lifecycle" for entries of this type. Used for differentiation from other access log entry types such as "http", "mirror", or "proxy"
request_id String yes The Cleversafe request UUID, a unique identifier generate for each request to assist with event correlation in the debug log.
time_start String yes

Time when the deletion for this object began.

Uses Apache Common Log format (e.g. 01/JAN/2020:00:00:00 -0700)
timestamp_start Integer yes Same as time_start but epoch time in milliseconds.
time_finish String yes

Time when the deletion for this object ended.

Uses apache common log format (e.g. 01/JAN/2020:00:00:00 -0700)
timestamp_finish Integer yes Same as time_finish but epoch time in milliseconds.
object_name String yes Name (or key) of the object that was deleted.
last_modified String yes

Last modified time of the object that was deleted.

Uses ISO 8601 format.
object_length Integer yes Size of the object that was deleted in bytes.
object_lifecycle ObjectLifecycle yes Contains object lifecycle data, which includes object expiration info as well as transition info (e.g. archive).