> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/data-and-dashboards/dashboards-and-insights/charts/donut-chart.md).
# Donut Chart
## Introduction
The **Donut Chart** displays data of one series in a donut with each piece being the size of proportioned amount of the total amount:
## Expected Data and Graph Designer
The Donut Chart expects data in a two column format such as:
| Type | Value |
| ---- | ------------- |
| a | 37
|
| b | 28
|
| c | 42
|
| d | 78 |
In the Graph Designer you can then select the column you want to use for your x-axis, which in this case is the different sections of the donut:
Hence, the x-axis column does not need to be the first column. However, for consistency purposes it is recommended to always use your first column for the x-axis.
The size of each donut piece will be automatically calculated and if you activate the **tooltip**, which you can do in the Graph Designer:
You can see the exact percentage as well as the absolute amount for each donut piece:
---
# 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.locoia.com/data-and-dashboards/dashboards-and-insights/charts/donut-chart.md?ask=&goal=
```
`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.