Contact UsGet started

Getting expense details by folder

Written by
Updated at November 20, 2024

You can get a CSV file with your general or per-resource spending details. You can download the file once or set up regular export.

One-time export

  1. Go to Yandex Cloud Billing.

  2. Select the account you want to get details for.
  3. In the left-hand panel, select Usage details.
  4. Click Export to CSV.
  5. Select the time period to get the details for.
  6. Click Download.

Setting up regular export

Getting started

  1. If you do not have any folders yet, create one. In the folder name, specify the project or client to use the folder.

  2. Create a bucket in Yandex Object Storage. Yandex Cloud will save detail files to this bucket. You can save details in multiple buckets.

    Alert

    Bucket requirements:

    • Do not make your bucket public; otherwise, anyone will be able to download your expense details from the bucket link.
    • Do not add encryption to the bucket.

  3. Make sure you have one of the following roles: billing.accounts.owner, billing.accounts.admin, or billing.accounts.editor.

Get expense details

  1. Go to Yandex Cloud Billing.

  2. Select the account you want to get details for.
  3. In the left-hand panel, select Export details.
  4. Click Create periodic export.
  5. In the Create periodic export window that opens, specify:

    • In the Bucket field, the name of the bucket to store the CSV file with details.

    • In the Directory field, the name of the folder for the file. It must end with the / character.

    • Select the language for product names: English or Russian.

    • Select General or Resource as the detailed view type.

      Tip

      If you select the Resource type of details for regular export, you can also view Yandex DataLens, Yandex Tracker, and DataSphere resources in the resource_id field (e.g., DataSphere community IDs).

  6. Click Create.

A new file with details is created in the bucket daily. The file name contains the prefix and date that details are collected for. The file is overwritten and updated with new data every hour.

The information can be updated in any daily file within a month.

Tip

Files with details from buckets are not deleted automatically, but you can configure scheduled deletion. For more information, see Object lifecycle (Object Storage refers to files in a bucket as objects).

Expense details file format

An uploaded file with details is a CSV table with comma-separated columns. Each row shows the product consumption level per day for the specified folder.

The table contains the following columns:

  • billing_account_id: Billing account ID.
  • billing_account_name: Billing account name.
  • cloud_id: ID of the cloud covered by the details.
  • cloud_name: Cloud name.
  • folder_id: Folder ID.
  • folder_name: Name of the folder at the time of exporting the details. This field may be empty if you deleted the folder before exporting the details.
  • resource_id: Resource ID, resource name, or subscription ID. The value of this field may be empty if the use of the service refers to the entire folder or it does not contain any resources. The services and resource_id column values are mapped as follows:
    • Compute Cloud and Cloud Marketplace: ID of the VM, disk snapshot, disk image, or other resource installed using Cloud Marketplace.
    • Object Storage: Bucket name.
    • Virtual Private Cloud: ID of the resource that processes incoming or outgoing traffic.
    • KMS: Key ID.
    • Network Load Balancer: Load balancer ID.
    • Container Registry: Container ID.
    • Kubernetes and Yandex Data Processing: Cluster ID.
    • Managed Service for PostgreSQL, Managed Service for ClickHouse®, Managed Service for MongoDB, Managed Service for MySQL®, Managed Service for Redis, and Managed Service for Apache Kafka®: Host ID in the cluster.
    • Message Queue: Request ID.
    • Cloud Functions: Function ID.
    • Monitoring, DataLens, Yandex IoT Core, SpeechKit, Translate, and Vision OCR: Empty value.
    • Technical support: Subscription ID.
  • service_id: ID of the service the consumed product belongs to.
  • service_name: Name of the service the consumed product belongs to.
  • sku_id: Consumed product ID.
  • sku_name: Product name.
  • date: Consumption charge date. A date is defined as an interval from 0:00 to 23:59 (UTC+3).
  • currency: Billing account currency. The possible values are RUB, USD, and KZT.
  • pricing_quantity: Number of product units consumed. The decimal separator is a period.
  • pricing_unit: Product consumption unit.
  • cost: Total cost of consumption. The decimal separator is a period.
  • credit: Total discounts. The decimal separator is a period.
  • monetary_grant_credit: Grant discount, including the platform introduction grant. The decimal separator is a period.
  • volume_incentive_credit: Consumption volume discount. The decimal separator is a period.
  • cud_credit: Discount for the committed resource volume. The cost of the consumption volume above the commited one equals the difference between the cost and credit column values. The decimal separator is a period.
  • misc_credit: Other types of discounts, including discounts for consumption after the platform introduction grant expires but before switching to the paid version. The decimal separator is a period.
  • label.user_labels.<label_name>: Labels added to the resources. For information about how to manage labels, see Managing labels.
  • locale: Language of each exported line. This field's value determines the sku_name column language. The possible values are en and ru.
  • updated_at: Date and time of the last line update in Unix Timestamp format.
  • exported_at: Date and time when the line was added to the details file.
Deprecated parameters
  • created_at: Date and time when the specified consumption charge was made, provided in Unix Timestamp format.
  • label.system_labels.folder_id: Folder ID. The value is now displayed in the folder_id column.
See also

ClickHouse® is a registered trademark of ClickHouse, Inc.

Previous
Viewing usage details in the console
Next
Viewing usage details in Yandex DataLens