> 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/desktop-client/reporting/diagrams.md).

# Diagrams

Discover comprehensive reporting features in the Desktop Client, including powerful diagram tools. Learn how to visualize and analyze data efficiently with our detailed method guide.

Diagrams are charts which are based on the data available in the report. Here, you need to be careful because even if a diagram is put into a band, the data used in this diagram is taken from the entire report. To be able to draw a diagram just based on the data available within one band, you need to manipulate the filter of the diagram by script, best done with the Before Print event.  

<figure><img src="http://aquawiki.andagon.com/pictures/drex_diagrams_2_custom.png" alt=""><figcaption></figcaption></figure>

**Example: Number of defects by significance**

<figure><img src="http://aquawiki.andagon.com/pictures/drex_diagrams_2_custom_2.png" alt=""><figcaption></figcaption></figure>

* The connection of data with diagrams is established with rows
* Every row contains a grouping argument (x-axis) and a value (y-axis) which is normally calculated with a sum function&#x20;
* For the use of 2D diagrams, you can define several rows.&#x20;


---

# 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/desktop-client/reporting/diagrams.md?ask=<question>&goal=<user_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.