Skip to main content
Outside service Partner
Hitachi Vantara Knowledge

Generating chargeback reports


You can generate chargeback reports from the Tenant Management Console. A chargeback report contains current and historical statistics about the tenant and its namespaces, broken out by hour.

Chargeback reports are a good source of information for namespace analysis, enabling you to adjust storage and bandwidth allocations based on usage patterns. These reports can also serve as input to billing systems that need to determine charges for capacity and bandwidth usage.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

About chargeback reports


A chargeback report contains statistics for each namespace owned by the current tenant. It also contains aggregated namespace statistics for the tenant. For example, the total number of reads for the tenant during a given reporting interval is the total number of successful read operations that occurred during that interval in each of the tenant's namespaces.

When generated from the Tenant Management Console, chargeback reports are in CSV format. Each line in a report contains the values for one namespace or for the tenant during one instance of the reporting interval.

The lines in a chargeback report are ordered alphabetically by namespace name. The lines for the tenant are at the end of the report. Multiple lines for a namespace or the tenant are ordered in ascending chronological order.

For information on how chargeback data is collected, see Chargeback statistics collection. For information on the contents of chargeback reports, see Chargeback report content.

RoleWebHelp.png

Roles: To generate chargeback reports, you need the monitor or administrator role.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Generating a chargeback report


You use the Chargeback page in the Tenant Management Console to generate chargeback reports. From this page, you can generate an hourly, daily, or monthly report:

An hourly report includes statistics for the most recent full hour, plus the statistics accumulated so far for the current hour. For example, if you request the report at 2:30:15 p.m., it will contain one set of statistics for the period of time between 1:00:00 p.m. and 1:59:59 p.m. and another set of statistics for the period of time between 2:00:00 p.m. and 2:30:15 p.m.

A daily report includes statistics for the most recent full day, plus the statistics accumulated so far for the current day. For example, if you request the report at 2:30:15 p.m. on October 7th, it will contain 24 sets of statistics for the period of time between 00:00:00 and 23:59:59 on October 6th and 15 sets of statistics for the period of time between 00:00:00 and 2:30:15 p.m. on October 7th.

A monthly report includes statistics for the past 30 days, plus the statistics accumulated so far for the current day. For example, if you request the report at 2:30:15 p.m. on October 7th, it will contain 24 sets of statistics for each of the past 30 days and 15 sets of statistics for the period of time between 00:00:00 and 2:30:15 p.m. on October 7th.

NoteWebHelp.png

Note: The statistics reported for the current hour may not reflect some reads and writes that have already occurred during the hour. After the hour is past, however, the statistics reported for it are complete.

TipWebHelp.png

Tip: You can use the HCP management API to generate chargeback reports that cover longer time periods and are in XML, JSON, or CSV format. This allows you to create applications that generate chargeback reports at regular intervals and feed those reports to a billing system. For information on using the management API to generate chargeback reports, see HCP Management API Reference.

RoleWebHelp.png

Roles: To generate a chargeback report, you need the monitor or administrator role.

To generate a chargeback report:

1.In the top-level menu of the Tenant Management Console, select Monitoring Chargeback.

2.On the Chargeback page, click on Hourly Chargeback Report, Daily Chargeback Report, or Monthly Chargeback Report, as applicable, and select the browser-specific option for downloading the report.

By default, the name of the downloaded report file is either Hourly-Chargeback-Report.csv, Daily-Chargeback-Report.csv, or Monthly-Chargeback-Report.csv, as applicable.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Chargeback statistics collection


Chargeback statistics either reflect a point in time or are dynamic. Point-in-time statistics are measurements taken at the end of a reporting interval, such as the used storage capacity for a namespace at the end of an hour. Dynamic statistics are measurements, such as the number of reads or writes to a namespace, that are accumulated over time.

HCP accumulates dynamic statistics on an hourly basis, starting at the beginning of each hour. So, for example, one statistic might represent the number of successful writes to a namespace that occurred between 11:00:00 and 11:59:59. Another might represent the number of successful writes to the same namespace that occurred between 12:00:00 and 12:59:59.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Chargeback report content


The first line of a chargeback report contains identifiers for the values in the subsequent lines. The table below 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 or to any of the namespaces owned by the tenant 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 or from any of the namespaces owned by the tenant 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:

true — For a namespace only, the namespace was deleted after the statistics in the set were collected.

false — The namespace or tenant currently exists.

included — For a tenant only, the statistics in the set include values for one or more namespaces that were subsequently deleted.

deletes

D

The total number of delete and purge operations successfully performed in the given namespace or in any of the namespaces owned by the tenant 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.

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 or to any of the namespaces owned by the tenant.

multipartObject
  Bytes
P The total number of bytes of object data in all the parts of multipart objects currently stored in the given namespace or in all the namespaces owned by the tenant.
multipartObject
  Parts
P The total number of parts of multipart objects currently stored in the given namespace or in all the namespaces owned by the tenant.
multipartObjects P The total number of multipart objects currently stored in the given namespace or in all the namespaces owned by the tenant.
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 or in all the namespaces owned by the tenant.

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 or in all the namespaces owned by the tenant.

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 or in all the namespaces owned by the tenant.

namespaceName

N/A

The name of the namespace to which the set of statistics in the line applies.

In lines that contain tenant statistics, this field has no value.

objectCount

P

The number of objects in the given namespace or in all the namespaces owned by the given tenant.

Each version of an object counts as a separate object. The object count does not include object versions that are delete markers.

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 or in any of the namespaces owned by the given tenant 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-dd hh:mm:ss

hh is hours on a 24-hour clock.

For example: 2010-10-07 14:00:00

storageCapacity
  Used

P

The total number of bytes occupied by stored data in the given namespace or in any of the namespaces owned by the given tenant. This includes object data, metadata, and any redundant data required to satisfy the applicable service plan.

Used storage capacity includes storage occupied by the parts of in-progress multipart uploads that have already been written to HCP. Used storage does not include replaced parts of multipart uploads, parts uploaded for aborted multipart uploads, or unused parts of completed multipart uploads.

systemName

N/A

The HCP domain name used for access to the content of namespaces owned by the given tenant

tenantName

N/A

Either:

The name of the tenant that owns the namespace to which the set of statistics in the line applies

The name of the tenant to which the set of statistics in the line applies

valid

N/A

The status of the set of statistics in the line. Possible values are:

true — HCP successfully collected all statistics in the set.

false — The statistics in the set do not reflect all the activity that occurred during the reporting interval. This may be due, for example, to a network failure or to other hardware issues.

writes

D

The total number of write operations successfully performed in the given namespace or in any of the namespaces owned by the given tenant 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.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Sample chargeback report


Here's an example of a daily chargeback report, where the report was requested for February 17, 2017, through February 18, 2017. The report shows statistics for the europe tenant, which owns the finance and hr namespaces. The report is shown as it would appear in a spreadsheet.

systemName tenantName namespaceName startTime endTime objectCount IngestedVolume storageCapacityUsed bytesIn bytesOut reads writes deletes multipartObjects multipartObjectParts multipartObjectBytes multipartUploads multipartUploadParts multipartUploadBytes deleted valid
hcp.example.com europe finance 2/17/2017 0:00:00 2/17/2017 23:59:59 6 134243721 134270976 123986263 87561 1 10 0 2 7 93213889 0 0 0 FALSE TRUE
hcp.example.com europe finance 2/18/2017 0:00:00 2/18/2017 23:59:59 15 186496747 186548224 52253026 0 0 12 0 3 11 132662065 0 0 0 FALSE TRUE
hcp.example.com europe hr 2/17/2017 0:00:00 2/17/2017 23:59:59 7 9609368 9621504 9609368 0 0 7 0 0 0 0 0 0 0 FALSE TRUE
hcp.example.com europe hr 2/18/2017 0:00:00 2/18/2017 23:59:59 15 19707387 19730432 10098019 0 0 8 0 0 0 0 0 0 0 FALSE TRUE
hcp.example.com europe   2/17/2017 0:00:00 2/17/2017 23:59:59 13 143853089 143892480 133595631 87561 1 17 0 2 7 93213889 0 0 0 FALSE TRUE
hcp.example.com europe   2/18/2017 0:00:00 2/18/2017 23:59:59 30 206204134 206278656 62351045 0 0 20 0 3 11 132662065 0 0 0 FALSE TRUE

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Chargeback page graphs


The Chargeback page contains four graphs. These graphs show information about the usage of the tenant's namespaces during the past 30 days (or since HCP was installed if that was less than 30 days ago).

The graphs are:

Writes (bytes) — Shows the number of bytes of data written to the tenant's namespaces.

The number of bytes written includes all parts written 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.

For more information on multipart uploads, see Working with multipart uploads.

Writes (operations) — Shows the number of successful write operations that targeted the tenant's namespaces.

Each write 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.

Reads (bytes) — Shows the number of bytes of data read from the tenant's namespaces.

Reads (operations) — Shows the number of read operations that targeted the tenant's namespaces.

A read of a multipart object counts as a single read operation.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.