B2 Usage Reports
- Print
- DarkLight
B2 Usage Reports
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Usage Reports provide a daily, detailed ledger of Backblaze B2 Cloud Storage usage. They are available to customers using Accounts (Individual), Groups, and Organizations. Usage Reports for Accounts and Groups can be enabled by contacting our support team or your account representative. These reports help calculate customer fees based on stored data and any applicable transaction fees.
For all Backblaze API operations and their corresponding documentation, see API Documentation.
Usage Reports for Organizations
To enable Usage Reports, sign in to your organization and select Organization > Reports > Report Settings in the left navigation menu. During enablement, select the region in which you want the Usage Reports to be stored.
Two CSV file types are generated daily for each organization: “Locations” and “Usage”. The “Usage” file contains the amount of storage used and other usage data. The “Locations” file provides a list of files that are generated daily and is primarily for reference purposes.
Usage Reports are generated for all regions and associated buckets within an organization.
Files for each day are organized into folders named by the {date} (YYYY-MM-DD format) and are uploaded to a special bucket. That bucket is auto-generated by Backblaze after the files are available for the Usage Report-enabled administrator account. The bucket name follows the format "b2-reports-$ACCOUNTID" where “$ACCOUNTID” is a Backblaze identifier for the regional storage account where reports are stored.
Locations File
The “Locations” file name convention is usage.{resource_name}.reportingLocations.csv. The file contains a header row with the column names and descriptions below.
| date | Dates in YYYY-MM-DD format and in UTC. |
| group_id | Empty. |
| line_version | The revision number of the format. Usually, this is incremented when the number of columns changes. |
| report_file_name | File name for each "Usage" file to expect per region. |
| reporting_location | Region. For example, us-west or us-east. |
| resource_name | Subscription identifier. |
Usage File
The Usage Report file name convention is a usage.{resource_name}.{reporting_location}.csv. One file is generated per region.
In the “Usage” file, rows dedicated to account-level transactions are included. The transactions api_txn_class_a/b/c are included in these rows since Backblaze B2 attributes them to the region level instead of the bucket level.
If a bucket does not have any usage to report, that bucket will not appear in the “Usage” file.
The file contains a header row with the column names and descriptions below.
| account_email | Empty. |
| account_id | Backblaze account identifier for account where the Usage Reports are stored, alphanumeric. |
| api_txn_class_a | Number of Class A transactions. Class A transactions are free of charge. |
| api_txn_class_b | Number of Class B transactions. API transactions are a billable entity. Number includes the free allocated amount. |
| api_txn_class_c | Number of Class C transactions. API transactions are a billable entity. Number includes the free allocated amount. |
| bucket_id | Bucket identifier, alphanumeric. |
| bucket_name | Name of the bucket. |
| date | Dates in YYYY-MM-DD format, indicating the UTC day covered by the report. |
| deleted_gb | Number of bytes deleted in gigabytes. |
| downloaded_bytes | Number of bytes downloaded in bytes. Number of bytes downloaded is a billable entity. Number includes the free allocated amount. |
| downloaded_favored_bytes | Number of favored bytes downloaded in bytes. Backblaze does not charge for favored bytes. |
| downloaded_gb | Number of bytes downloaded in gigabytes. |
| group_id | Empty. |
| line_version | The revision number of the format. Usually, this is incremented when the number of columns changes. |
| reporting_location | Region. For example, us-west or us-east. |
| resource_group_id | Resource Group identifier. |
| resource_group_name | Resource Group name. |
| resource_name | Subscription identifier. |
| storage_byte_hours | Number of byteHours stored. Number of stored byte hours is a billable entity. Number includes the free allocated amount. |
| stored_gb | Number of bytes stored in gigabytes (at the end of the day). |
| uploaded_gb | Number of bytes uploaded in gigabytes. |
The format of these files may change in the future. For example, additional columns may be added.
Usage Reports for Groups
Three CSV file types related to usage are generated daily for each Group: “Groups,” “Locations,” and “Usage”. The “Usage” file contains the amount of storage used and other usage data. The “Groups” and “Locations” files provide lists of files that are generated daily and are primarily for reference purposes.
- “Groups” file (file name:
usage.groups.csv): contains a list of Group identifiers and the corresponding “Locations” file names that you can expect to be generated for the day. - “Locations” file (file name structure:
usage.group-{groupId}.reportingLocations.csv): contains a list of regions. - “Usage” file (file name structure:
usage.group-{groupId}.{reportingLocation}.csv): contains the usage totals generated by each Group member for a given day.
Usage Reports are generated only for the Group members who are located within the same data region as the Group account.
Files for each day are organized into folders named by the {date} (YYYY-MM-DD format) and are uploaded to a special bucket. That bucket is auto-generated by Backblaze once files are available for the Usage Report-enabled administrator account. The bucket name follows the format "b2-reports-$ACCOUNTID" where “$ACCOUNTID” is a Backblaze administrator account identifier.
Groups File
The Groups file name is usage.groups.csv. The file contains a header row and the column names and descriptions below.
| date | Dates in YYYY-MM-DD format in UTC. |
| group_id | Group identifier, integer. |
| reporting_locations_file_name | File name of each "Locations" file to expect per Group. |
Locations File
The “Locations” file name convention is usage.group-{group_id}.reportingLocations.csv. The file contains a header row and the column names and descriptions below.
| date | Dates in YYYY-MM-DD format in UTC. |
| group_id | Group identifier, integer. |
| reporting_location | Region. For example, us-west or us-east. |
| report_file_name | File name for each "Usage" file to expect per Group. |
Usage File
The Usage file name convention is a usage.group-{group_id}.{reporting_location}.csv. One file per Group is generated. The file contains a header row and the data.
In the “Usage” file, a row dedicated to account-level transactions is included. api_txn_class_a/b/c are included in this row since Backblaze B2 attributes them to the account level and not the bucket level.
If a bucket does not have any usage to report, that bucket will not appear in the “Usage” file.
| account_email | Email address for Group member. |
| account_id | Backblaze account identifier for account where the Usage Reports are stored, alphanumeric. |
| api_txn_class_a | Number of Class A transactions. Class A transactions are free of charge. |
| api_txn_class_b | Number of Class B transactions. API transactions are a billable entity. Number includes the free allocated amount. |
| api_txn_class_c | Number of Class C transactions. API transactions are a billable entity. Number includes the free allocated amount. |
| bucket_id | Bucket identifier, alphanumeric. |
| bucket_name | Name of the bucket. |
| date | Dates in YYYY-MM-DD format, indicating the UTC day covered by the report. |
| deleted_gb | Number of bytes deleted in gigabytes. |
| downloaded_bytes | Number of bytes downloaded in bytes. Number of bytes downloaded is a billable entity. Number includes the free allocated amount. |
| downloaded_favored_bytes | Number of favored bytes downloaded in bytes. Backblaze does not charge for favored bytes. |
| downloaded_gb | Number of bytes downloaded in gigabytes. |
| group_id | Group identifier, integer. |
| line_version | The revision number of the format. Usually, this is incremented when the number of columns changes. |
| reporting_location | Region. For example, us-west or us-east. |
| resource_group_id | Resource Group identifier. |
| resource_group_name | Resource Group name. |
| resource_name | Subscription identifier. |
| storage_byte_hours | Number of byteHours stored. Number of stored byte hours is a billable entity. Number includes the free allocated amount. |
| stored_gb | Number of bytes stored in gigabytes (at the end of the day). |
| uploaded_gb | Number of bytes uploaded in gigabytes. |
The format of these files may change in the future. For example, additional columns may be added.
Usage Reports for Standalone Accounts
A single CSV file, “Usage,” is generated daily for an account. The “Usage” file contains the amount of storage used and other usage data.
The “Usage” file (file name structure: usage.account-{accountId}.csv) contains the usage totals generated by the account for a given day.
Files for each day are organized into folders named by the {date} (YYYY-MM-DD format), and are uploaded to a special bucket. That bucket is auto-generated by Backblaze once files are available for the Usage Report-enabled administrator account. The bucket name follows the format "b2-reports-$ACCOUNTID" where “$ACCOUNTID” is your Backblaze account identifier.
Usage File
The Usage file name convention is a usage.account-{account_id}.csv. One file is generated per account. The file contains a header row and the data.
In the “Usage” file, a row dedicated to account-level transactions is included. api_txn_class_a/b/c are included in this row since Backblaze B2 attributes them to the account level and not the bucket level.
If a bucket does not have any usage to report, that bucket will not appear in the “Usage” file.
| account_email | Email address. |
| account_id | Backblaze account identifier for the account, alphanumeric. |
| api_txn_class_a | Number of Class A transactions. Class A transactions are free of charge. |
| api_txn_class_b | Number of Class B transactions. API transactions are a billable entity. Number includes the free allocated amount. |
| api_txn_class_c | Number of Class C transactions. API transactions are a billable entity. Number includes the free allocated amount. |
| bucket_id | Bucket identifier, alphanumeric. |
| bucket_name | Name of the bucket. |
| date | Dates in YYYY-MM-DD format, indicating the UTC day covered by the report. |
| deleted_gb | Number of bytes deleted in gigabytes. |
| downloaded_bytes | Number of bytes downloaded in bytes. Number of bytes downloaded is a billable entity. Number includes the free allocated amount. |
| downloaded_favored_bytes | Number of favored bytes downloaded in bytes. Backblaze does not charge for favored bytes. |
| downloaded_gb | Number of bytes downloaded in gigabytes. |
| group_id | Empty. |
| line_version | The revision number of the format. Usually, this is incremented when the number of columns changes. |
| reporting_location | Region. For example, us-west or us-east. |
| resource_group_id | Resource Group identifier. |
| resource_group_name | Resource Group name. |
| resource_name | Subscription identifier. |
| storage_byte_hours | Number of byteHours stored. Number of stored byte hours is a billable entity. Number includes the free allocated amount. |
| stored_gb | Number of bytes stored in gigabytes (at the end of the day). |
| uploaded_gb | Number of bytes uploaded in gigabytes. |
The format of these files may change in the future. For example, additional columns may be added.
Usage Report Bucket
A Usage Report bucket is reserved strictly for the daily usage files and is therefore restricted. This means that the bucket cannot be modified (for example, it cannot be toggled between private and public) and no files can be uploaded to the bucket. You may store as many of the daily usage files in the bucket as you wish. Like any other bucket in your account, you will be charged every 30 days for the amount stored in the bucket and your account will be charged for downloads and transaction fees (see details here).
Backblaze performs a daily check on the bucket to verify the existence of files from the past seven days and restore any missing files if necessary.
The Reports page is for your convenience and displays the data within the Usage Reports bucket that is currently activated. If you switch the region for reports generation, the existing reports bucket in the original region will still be available from the Buckets page.
Third-party applications may not support restricted buckets. Do not delete files until they are at least seven days old because the system will regenerate them.
Was this article helpful?