> For the complete documentation index, see [llms.txt](https://neirth.gitbook.io/openlobster/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://neirth.gitbook.io/openlobster/dashboard.md).

# Dashboard

The Dashboard gives you an at-a-glance view of system health, active channels, recent conversations, and live logs.

The Dashboard is the first screen you see after logging in. It acts as a command center: you can check key metrics, confirm channels are online, see who is talking to the agent, and read live logs — all without leaving a single page.

## Panels at a glance

The dashboard is divided into six panels. Each is described in its own page in this section.

* [**Statistic Cards**](/openlobster/dashboard/stat-cards.md) — Key numbers: active sessions, messages sent and received, pending and completed tasks.
* [**Channels Panel**](/openlobster/dashboard/channels.md) — Online/offline status for each configured messaging channel (Telegram, Discord, etc.).
* [**System Status Panel**](/openlobster/dashboard/system-status.md) — Memory backend, secrets backend, and server uptime.
* [**Recent Conversations Panel**](/openlobster/dashboard/recent-conversations.md) — Latest user sessions with a shortcut to open them in the Chat view.
* [**MCP Servers Panel**](/openlobster/dashboard/mcp-servers.md) — Connection status and tool count for each connected MCP server.
* [**Recent Logs Panel**](/openlobster/dashboard/logs.md) — Live feed of INFO, WARN, and ERROR messages from the backend.

## When to use the Dashboard

{% hint style="info" %}
Make the Dashboard your first stop whenever something seems off. Most problems produce a visible signal here: a channel going offline, an error in the logs, or metrics that stop updating.
{% endhint %}

Use the Dashboard to:

* Confirm the system started correctly after a restart (check **Uptime** and **Health**).
* Verify that all channels are online before expecting users to interact.
* Monitor activity during a high-traffic period.
* Find the first clue about an incident before diving into logs or settings.


---

# 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://neirth.gitbook.io/openlobster/dashboard.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.