> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboard

> What the panel home page shows, how to read the health score, and where to go when problems occur.

The dashboard is the panel's home page. It answers three questions: “Is everything OK?”, “What happened in the last 24 hours?”, and “What should I do next?” Data refreshes automatically: the health summary and events every 30 seconds, node and Flow lists every minute, and sidebar badges every 15 seconds.

> [!NOTE]
>
> For panel administrators and SREs. Required permissions: Axottle administrator with read access.

## Health score

The dashboard header shows the overall health score: the proportion of healthy objects among everything monitored by the health system, including nodes, Flows, agents, routes, and WARP groups. At 100%, everything is healthy; a lower score means more objects are degraded or critical.

For how states are calculated and what each status means, see [Health](https://docs.axottle.com/en/health/overview.md) and [States](https://docs.axottle.com/en/health/states.md).

## Key metrics

The four cards below the header show:

| Card | What it shows | Highlight |
| - | - | - |
| **Configs** | Number of Flows and how many are healthy or have problems | Yellow for degraded, red for critical |
| **Healthy nodes** | Healthy nodes versus the total, for example `8/10` | Yellow for degraded, red for critical |
| **Agents** | Connected agents versus the total | Red if any agents are offline |
| **Open events** | Open health incidents and actions proposed by the system | Yellow if any events are open |

Read the cards from left to right as a diagnostic chain: a connection scheme problem is often caused by a node problem, which may in turn be caused by an offline agent.

## Needs attention

The Needs attention area shows health incidents from the last 24 hours that are still open. If it is empty, there are no open problems. Each incident links to [Health](https://docs.axottle.com/en/health/overview.md), where you can see the complete picture: probes, the timeline, and self-healing suggestions.

## Quick actions

The Quick actions card provides entry points to the main workflows:

* **Add node** → [Node installation](https://docs.axottle.com/en/nodes/installation.md)
* **Build a scheme** → [Flow builder](https://docs.axottle.com/en/connection-units/overview.md)
* **Install SelfSteal** → [Masking site](https://docs.axottle.com/en/security/masking.md)
* **Connect CDN** → [CDN](https://docs.axottle.com/en/cdn/overview.md)

## Event feed

The bottom of the dashboard shows a compact feed of recent events. The full version with filters is available in the [operations journal](https://docs.axottle.com/en/panel/journal-and-audit.md).

## Where to go when problems occur

> [card] [Health score dropped](https://docs.axottle.com/en/health/overview.md)
>
> Open Health to see which object and probe failed.

> [card] [Red Agents card](https://docs.axottle.com/en/nodes/troubleshooting.md)
>
> The agent is offline. Start with node diagnostics.

> [card] [Connection scheme problems](https://docs.axottle.com/en/connection-units/troubleshooting.md)
>
> Flow diagnostics and common errors.

> [card] [Many open events](https://docs.axottle.com/en/panel/journal-and-audit.md)
>
> The operations journal shows when each problem started.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.