> For the complete documentation index, see [llms.txt](https://help.meltingspot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meltingspot.io/english/manage-spot/dashboard/lives.md).
# Lives
Easily access and view all your live metrics in a single glance.
The table on this page allows you to view all the details of each live stream (including those that have been deleted) in one place.
{% hint style="info" %}
If you'd like to find out more about live metrics and how to access them, go to the live metrics page.
{% endhint %}
You can **filter and change the order of the table's columns** for a custom experience. Click on `Filters` or `Columns` to set up your dashboard.
**For a more in-depth analysis, you can export the data in .csv format** (Excel, Google Sheets) by clicking on the Download icon next to the filters.
The date of the last metrics update appears at the top right-hand corner to ensure you're always up to date with the latest information.
### Live activities & performance
Want to know more about the performance of a specific live ? Click on its name in the table to open the Activities record. Check this page for more detailed explanations :
{% content-ref url="/pages/Ni6G3HC7QiFoK6pJPqX0" %}
[Live performance metrics](/english/spot-content/lives/metrics.md)
{% endcontent-ref %}
---
# 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.meltingspot.io/english/manage-spot/dashboard/lives.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.
