# Chargeback Reporting

In order to get great chargeback reporting in the 6fusion Dashboard, it is very important to first understand how the data is used for chargeback processing.

6fusion's Dashboard has the ability to **FILTER** consumption data based upon the following main vCenter objects over any metered timeframe:

* **Datacenter**
* **Cluster**
* **Resource Pool**
* **ESX Physical Hosts**
* **Virtual Machines**

![](/files/-Lyp8EnyCG66rBmc264t)

This same **FILTER** ability is also applied to all the metrics that are being tracked, not just cost related ones - 6fusion also tracks the following key metrics:

* **Consumption (kWAC)**
* **Costs**
* **Virtual CORES**
* **CPU ( MHz)**
* **Memory (MB)**
* **Storage (GB)**
* **DISK IO (Kbps)**
* **IOPS**
* **Network IO (kbps)**
* **Virtual Machines**

![](/files/-Lyp974zPo22sInFp_S_)

## vSphere Architecture

We need to start by understanding how VMware can be setup with various objects and tags. There are many ways to configure a virtual environment and it is important to understand all the possibilities before you create your tagging system.

Here is a great overarching picture that best describes the many ways of organizing you're virtual machines.

![](/files/-LzJ95yD1vvHEpodaPig)

### Defining vCenter Tags

Its important to note that there are many different ways of organizing your infrastructure resources - the 6fusion collector will be able to pull the related object descriptions and associated tags that you have setup - the customer has full control of defining these objects and tags that will best fit their own organizational needs.

![](/files/-LzJAJ8Lr7w5v6KiTs2l)


---

# Agent Instructions: 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://documentation.6fusion.com/chargeback-reporting.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.