Chargeback report content
The first line of a chargeback report contains identifiers for the values in the subsequent lines. The following table describes each of these values and indicates whether it is point in time (P) or dynamic (D).
Identifier | Type | Value |
bytesIn | D |
The total number of bytes successfully written to the given namespace, to any of the namespaces owned by the given tenant, or to any of the HCP namespaces in the HCP system during the reporting interval. The total number of bytes written includes all parts uploaded for multipart uploads regardless of whether the upload of the part has finished, the part was subsequently replaced, the multipart upload was aborted, or the part was not used in the completed multipart upload. If data was compressed before being transmitted, this is the number of bytes before compression. |
bytesOut | D |
The total number of bytes read from the given namespace, from any of the namespaces owned by the given tenant, or from any of the HCP namespaces in the HCP system during the reporting interval. If data (including XML for directory listings) was compressed before being transmitted, this is the number of bytes before compression. |
deleted | N/A |
One of:
|
deletes | D |
The total number of delete and purge operations successfully performed in the given namespace, in all the namespaces owned by the given tenant, or in all the HCP namespaces in the HCP system during the reporting interval. A delete of a multipart object counts as a single delete operation. The count of delete and purge operations does not include automatic deletions of replaced parts, parts of aborted multipart uploads, or unused parts of completed multipart uploads. |
endTime | N/A | The end time of the reporting interval for the set of statistics in the line, in the same format as is used for the startTime value. |
erasureCoded Objects | P | The total number of erasure-coded objects and erasure-coded parts of multipart objects currently stored in the given namespace, in all the namespaces owned by the given tenant, or in all the HCP namespaces in the HCP system. |
ingestedVolume | P | The total size of the stored data and custom metadata, in bytes, before the data and custom metadata were added to the given namespace, to any of the namespaces owned by the given tenant, or to any of the HCP namespaces in the HCP system. |
metadataOnly Bytes | P | The total number of bytes of object data currently not stored for metadata-only objects in the given namespace, in all the namespaces owned by the given tenant, or in all the HCP namespaces in the HCP system. |
metadataOnly Objects | P |
The total number of objects that are currently metadata-only in the given namespace, in all the namespaces owned by the given tenant, or in all the HCP namespaces in the HCP system. A multipart object that is metadata-only counts as a single object. |
multipartObject Bytes | P | The total number of bytes of object data in all the parts of multipart objects currently stored in the given namespace, in all the namespaces owned by the given tenant, or in all the HCP namespaces in the HCP system. |
multipartObject Parts | P | The total number of parts of multipart objects currently stored in the given namespace, in all the namespaces owned by the given tenant, or in all the HCP namespaces in the HCP system. |
multipartObjects | P | The total number of multipart objects currently stored in the given namespace, in all the namespaces owned by the given tenant, or in all the HCP namespaces in the HCP system. |
multipartUpload Bytes | P |
The total number of bytes of object data in all the successfully uploaded parts of multipart uploads that are currently in progress in the given namespace, in all the namespaces owned by the given tenant, or in all the HCP namespaces in the HCP system. This number does not include bytes of data in replaced parts of multipart uploads, parts uploaded for aborted multipart uploads, or unused parts of completed multipart uploads. |
multipartUpload Parts | P |
The total number of successfully uploaded parts of multipart uploads that are currently in progress in the given namespace, in all the namespaces owned by the given tenant, or in all the HCP namespaces in the HCP system. This number does not include replaced parts of multipart uploads, parts uploaded for aborted multipart uploads, or unused parts of completed multipart uploads. |
multipartUploads | P | The total number of multipart uploads that are currently in progress in the given namespace, in all the namespaces owned by the given tenant, or in all the HCP namespaces in the HCP system. |
namespaceName | N/A |
The name of the namespace to which the set of statistics in the line applies. In lines that contain tenant or systemwide statistics, this field has no value. |
objectCount | P |
The number of objects in the given namespace, in all the namespaces owned by the given tenant, or in all the HCP namespaces in the HCP system. Each version of an object counts as a separate object. The object count does not include object versions that are delete markers. A delete marker is a special version of an object that indicates that a version of the object has been deleted. A delete marker has a version ID but does not have any data or metadata. Each multipart object counts as a single object. Objects that are in the process of being created by multipart uploads are not included in the object count. |
reads | D |
The total number of read operations performed in the given namespace, in all the namespaces owned by the given tenant, or in all the HCP namespaces in the HCP system during the reporting interval. A read of a multipart object counts as a single read operation. |
startTime | N/A |
The start time of the reporting interval for the set of statistics in the line, in this format: yyyy-MM-ddhh:mm:ss hh is hours on a 24-hour clock. For example: 2017-10-07 14:32:47 |
storageCapacity Used | P |
The total number of bytes of primary running storage occupied by stored data for the given namespace, for all the namespaces owned by the given tenant, or for all the HCP namespaces in the HCP system. This includes object data, system and custom metadata, and any redundant data required to satisfy the applicable service plan. Used storage capacity also includes storage occupied by the parts of in-progress multipart uploads that have already been written to HCP. Used storage capacity does not include replaced parts of multipart uploads, parts uploaded for aborted multipart uploads, or unused parts of completed multipart uploads. |
systemName | N/A |
One of:
|
tenantName | N/A |
Either:
In lines that contain systemwide statistics, this field has no value. |
tieredBytes | P |
Total number of bytes of object data currently stored on primary spindown storage (if the system includes spinddown storage), on S Series, or on extended storage for the given namespace, for all the namespaces owned by the given tenant, or for all the HCP namespaces in the HCP system. On S Series only, the total number of bytes includes parts of in-progress multipart uploads regardless of whether the upload of the part has finished. This number does not include replaced parts of multipart uploads, parts uploaded for aborted multipart uploads, or unused parts of completed multipart uploads. |
tieredObjects | P |
The total number of objects with data currently stored on primary spindown storage (if the system includes spindown storage), on S Series, or on extended storage for the given namespace, for all the namespaces owned by the given tenant, or for all the HCP namespaces in the HCP system. Each part of a multipart object counts as a separate object and, on S Series only, each part of an in-progress multipart upload counts as a separate object. |
valid | N/A |
The status of the set of statistics in the line. Possible values are:
|
writes | D |
The total number of write operations successfully performed in the given namespace, in all the namespaces owned by the given tenant, or in all the HCP namespaces in the HCP system during the reporting interval. Each upload of a part for a multipart upload counts as a separate write operation. This applies even if the part was subsequently replaced, the multipart upload was aborted, or the part was not used in the completed multipart upload. |