> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.3/vizpads-explore/time-taken-to-load-a-chart/chart-level.md).

# Chart level

Learn how to enable or disable query time for individual charts in a Vizpad and view detailed execution breakdowns for faster, clearer analysis.

Here are the steps to manage the display of time taken to load a chart:

1. While editing a Vizpad, click on an individual chart to show/hide query execution time on that specific chart.

<figure><img src="https://files.helpdocs.io/6dnnwn52e3/articles/v9x5jecjf7/1688108984491/image.png" alt="" width="188"><figcaption><p>Show query time toggle for a chart</p></figcaption></figure>

2. In the right Configuration pane, if **Show Query Time** toggle is enabled, then a three-dot kebab menu will appear on the top right corner of the chart.&#x20;
3. Click on the three-dot menu, and the time taken to execute a query will be displayed. Click on **Query Time Details** to view the breakdown of the time taken.

<figure><img src="https://files.helpdocs.io/6dnnwn52e3/articles/v9x5jecjf7/1688114513682/image.png" alt="" width="375"><figcaption><p>Query time displayed in chart menu</p></figcaption></figure>


---

# 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://help.tellius.com/tellius-6.3/vizpads-explore/time-taken-to-load-a-chart/chart-level.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.