> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/dashboards/creating-a-chart.md).
# Creating a chart
Learn how to create charts in dashboards with step-by-step instructions, tips for customization, and visuals for effective data visualization in Aqua Cloud.
To add a chart, click on Add widget in the middle of the screen if it is a new dashboard, or on the  button on the top right. Give it a title. Select the project or subfolder for the data you want to include.
Creating a chart on the dashboard
In the configuration, you can specify the element to be displayed on the chart, and you can also select which field to group the elements by. If you have already created some pre-saved filter conditions known as views, you can copy these filters by selecting the appropriate view and filter the data on the chart. Furthermore, you can configure your own filter conditions and groups. You can also choose whether to display the legend, totals or percentages on the chart.
Chart configuration
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.aqua-cloud.io/documentation/dashboards/creating-a-chart.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
