> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/workspace/live-servers.md).

# Live Servers

**Dashboard → Live Servers** shows real-time telemetry from the servers running your application. It is a live view: data streams only while you watch and is not stored.

Each reporting server appears as a card with a live indicator and charts for:

* **CPU** — current utilization.
* **Memory** — total process memory.
* **Sessions** — active user sessions.
* **Memory / session** — memory divided by active sessions.
* **Threads** — thread count.
* **GC heap (MB)** — managed heap size over time.

Several servers can report into the same project — for example a developer machine and a staging server side by side.

## Connect a server

Live Servers uses the same telemetry agent as load testing — set it up once in **Settings → Telemetry** and you get both: see [Server telemetry](/load-testing/server-telemetry.md) for the framework snippets. Once the agent runs in your application, the server appears here within seconds of starting.

{% hint style="info" %}
Open Live Servers while a [load test](/load-testing.md) runs to watch CPU, memory, and sessions respond as virtual users replay your features.
{% endhint %}


---

# 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.testvibe.com/workspace/live-servers.md?ask=<question>&goal=<endgoal>
```

`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.