> For the complete documentation index, see [llms.txt](https://docs.gptboost.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gptboost.io/features/summary-and-metrics.md).
# Summary & Metrics
Request and token counts, latency and cost reports that bring clarity and predictability to your AI application. Our graphical dashboard provides an insightful representation of various key metrics:
1. **Request Status Breakdown:** Easily distinguish between successful and failed requests in a single chart, offering a clear overview of your LLM's performance.
2. **Latency Analysis:** Monitor latency trends over time to ensure optimal response times.
3. **Tokens:** Visualize tokens usage, helping you identify potential critical levels and optimize your LLM.
4. **Cost Tracking:** Keep a close eye on cost trends associated with your LLM, enabling effective budget management and cost control.
These comprehensive visualizations empower you to see the bigger picture, make informed decisions and optimize your LLM app's costs and performance. Ultimately you get to ensure business value is delivered to your users and there is ROI for your business from your LLM-powered product
---
# 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.gptboost.io/features/summary-and-metrics.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.