> For the complete documentation index, see [llms.txt](https://docs.float16.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.float16.cloud/getting-started/account/dashboard.md).

# Dashboard

Our application features the Activity Dashboard. These dashboards provide users with comprehensive insights into their service usage and activities.

## Activity Dashboard

<figure><img src="/files/jITolLRHW6BsnksgmRH7" alt=""><figcaption><p>Activity Dashboard</p></figcaption></figure>

Provides detailed insights into user activities for each individual service, filtered by month (default: current month, up to 12 months of historical data available).

### Location

* Accessible within the Services, appears as a side menu "Activity".&#x20;

### Features

#### LLM as a Service

The dashboard includes four main components:

1. **Prompt Usage**: Daily prompt token usage across all models
2. **Completion Usage**: Daily completion token usage across all models
3. **API Requests**: Daily REST requests across all models

{% hint style="info" %}
Bars represent daily usage, with colors distinguishing between models.
{% endhint %}

4. **Activity Log**: Tabular view of all activities across all models, grouped hourly. Includes timestamps, requests, prompt usage, completion usage and average time for comprehensive usage tracking and analysis.

#### One Click Deploy

The activity dashboard appears in each instance, displaying individual instance activity logs. The dashboard comprises three main components:

1. **Token Usage**: Visualizes daily token consumption for this model instance. Each bar represents daily usage, with distinct colors differentiating between prompt and completion token usage.
2. **API Requests**: Illustrates daily REST requests made to this model.
3. **Activity Log**: Tabular view of all activities happen in this model instance, grouped hourly. Includes timestamps, requests, prompt usage, completion usage and average time for comprehensive usage tracking and analysis.

You can download your activity log as a CSV file. This log is organized hourly and separated by model. To access this feature, simply click the "Download CSV" button in the top of Activity Dashboard page.

#### Serverless GPU

The Activity dashboard appears in each project's activity section and provides a visual summary of usage and cost metrics. It consists of **four main components**:

1. **Total Cost:** Displays the total accumulated cost during the selected time range. The cost is categorized into three types: On-Demand, Spot and Storage.
2. **Total Usage:** Shows the total GPU compute time consumed, measured in seconds. Separates usage into On-Demand and Spot
3. **Cost Over Time (Graph):** A bar chart that visualizes daily cost over the selected month. Each bar is broken down by cost type: On-Demand, Spot, and Storage
4. **Tasks (Graph):** A daily breakdown of the number of tasks run within the selected period, categorized by Manual, Function, Server, and Spot triggers


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.float16.cloud/getting-started/account/dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.