# Charges Menu

The Charges option allows users to view and analyze the detailed history of resource usage for which charges have been incurred. This feature is highly useful for tracking resource consumption over specific periods.

<figure><img src="/files/x1zRfxWZhToqIreOdpdr" alt=""><figcaption></figcaption></figure>

## How to Use

1. To review resource usage history, select the Charges option from the Billings menu.
2. You will be prompted to select a Period for the data retrieval. Choose the desired date. For this example, September 1, 2025, is selected.

<figure><img src="/files/weBQXwom84vMwLNF8KRm" alt=""><figcaption></figcaption></figure>

3. Click the Load Charges button to display the data.

<figure><img src="/files/bSgHl2I14PATQPcWT6hU" alt=""><figcaption></figcaption></figure>

Upon successful loading, the system will present the output in a table format with the following columns:

* Start Time (UTC): The timestamp when the charge calculation for the resource began.
* End Time (UTC): The timestamp when the charge calculation for the resource ended.
* Name: The specific name of the resource being used (e.g., the name of a Notebook or Pod).
* Resource Type: The type of resource consumed (e.g., CPU, RAM, Storage, GPU).
* Charge (Unit Hour): The total charge, calculated by multiplying the number of resource units by the duration of usage in hours within the selected time frame.

<figure><img src="/files/Q1YLkrWCgA3WEw28b9eg" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cloudeka.ai/guidance-for-individual/deka-gpu-mlops/billing-and-charging-dashboard/charges-menu.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.