Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. IT Analytics Help
  3. Section V. Report Reference
  4. Capacity Chargeback Reports
  5. Object Store Chargeback

Object Store Chargeback

Explore your data center using customizable report templates or by using parts of your IT infrastructure as entry points. Use Search to find reports, templates and dashboards across the portal.

Use the Reports tab to examine the catalog of templates, dashboards and reports - organized by products along with user-created, and system folders. This report is located here:

Capacity Manager > Chargeback and Billing > Object Store Chargeback

View hourly dynamic statistics for a tenant's namespace or a user's volume or file system. Use this report to identify ingested volumes, used capacity, and number of reads/writes. For example, this report is relevant for Hitachi Content Platform (HCP) chargeback.

Table: Object Store Chargeback

Column name

Description

Cluster/Array

Name of the storage array.

Model

Storage array family.

Tenant/User

Name of the tenant.

# of Namespaces

Number of namespaces owned by the tenant. Click the link to view namespace-level statistics.

Start Date

The start time of the reporting interval for the set of statistics.

End Date

The end time of the reporting interval for the set of statistics.

# of Objects

The total number of objects and versions stored in the namespace.

Ingested Volume

Amount of stored data and custom metadata before it was added to the namespace. The total size of the stored data and custom metadata, in bytes, before it was added to the identified namespace, to any of the namespaces owned by the identified tenant, or to any of the namespaces in the system.

Used Capacity

The amount of storage currently occupied by all data stored in the namespace, including object data, metadata, and any redundant data. Values are stored as KiB in the database and rendered according to your user profile preferences.

Bytes In

Number of KB read from the namespace. The total number of KB read from the identified namespace, from any of the namespaces owned by the identified tenant, or from any of the namespaces in the 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.

Bytes Out

Number of KB written to the namespace. The total number of KB successfully written to the identified namespace, to any of the namespaces owned by the identified tenant, or to any of the namespaces in the system during the reporting interval. If data was compressed before being transmitted, this is the number of bytes before compression.

# of Reads

Number of namespace reads. The total number of read operations performed in the identified namespace, in all the namespaces owned by the identified tenant, or in all the namespaces in the system during the reporting interval.

# of Writes

Number of namespace writes. The total number of write operations successfully performed in the identified namespace, in all the namespaces owned by the identified tenant, or in all the namespaces in the system during the reporting interval.

Deleted?

Namespace or tenant delete status.

Valid?

The status of the set of statistics in the line.

Possible values: true = All statistics in the set have been successfully collected by the system.. 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 one or more nodes being unavailable during that time, to a network failure, or to other hardware issues.

Last Updated

The date and time the node data was last updated in the IT Analytics database.

Feedback

Was this page helpful?
Previous

Policy Detail

Next

Object Store Chargeback Detail

Feedback

Was this page helpful?