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

# Home

> Read the health of data intake, the alerts that fire, who is on call, and what to set up next, on one page.

**Home** is the first page after sign-in unless the personal start page is changed. It answers
three questions for the current workspace: is data arriving, is anything firing, and who is on
call. Each part shows only what the permissions of the account allow.

## The head of the page

| Control | Purpose |
| - | - |
| **Quick start** | Opens the setup steps of the workspace. See [Quick start](#quick-start). |
| **Last 24 hours** / **Last 7 days** | The period of the volume figures, the health chart, and the stream rates. |
| **Refresh** | Loads every part again. **Updated** shows when the figures were read. |
| **New** | Creates a dashboard, an alert rule, a stream, a pipeline, or a function. |

When critical incidents fire, a banner above the page lists them. **View all** opens
[Alerts](https://docs.molesignal.com/en-US/alerting).

## Intake verdict and key figures

The strip at the top sums up data intake in one sentence and gives the next action. The worst
[state](#system-health-and-priority-streams) among the streams decides, in this order:

| Verdict | Meaning | Action |
| - | - | - |
| **No data connected yet** | The workspace has no stream. | **Connect a data source** opens [Datasource](https://docs.molesignal.com/en-US/intake). |
| **Streams interrupted** | At least one stream is interrupted. | **Investigate intake** |
| **Some streams are delayed** | At least one stream is delayed. | **Review delayed streams** |
| **Data is stale** | At least one stream is stale. | **Check data intake** |
| **Status unknown** | The state of the streams cannot be read. | **Try again** |
| **Intake is healthy** | The streams that have data are healthy. | **View streams** |
| **No data yet** | Streams exist, but none has received data. | **Connect a data source** |

**Ask Mole Agent** hands the verdict to [Mole Agent](https://docs.molesignal.com/en-US/agent) with a prompt that asks for the
likely causes and the first checks.

Beside the verdict:

| Figure | Shows |
| - | - |
| **Active alerts** | Incidents that fire, and how many of them are acknowledged. |
| **Raw intake volume** | The bytes received in the period, the rate, and the number of events. |
| **Compressed data size** | The stored size, and how much smaller it is than the raw intake. |

## Quick start

The quick start strip shows the next setup step until all of them are done. **Complete setup**
opens the list:

| Step | Done when |
| - | - |
| **Connect a datasource** | The workspace has a stream. |
| **Create a dashboard** | The workspace has a dashboard. |
| **Create an alert** | The workspace has an alert rule. |
| **Automate a pipeline** | The workspace has a pipeline. |
| **Load sample data** | The sample streams exist. |

**Load** writes a small set of related sample data into three streams: `sample_app_logs`,
`sample_app_metrics`, and `sample_app_traces`. The traces follow calls from `frontend` through
`checkout` and `payment` to `db`, the logs carry the same `trace_id`, and the metrics give the
latency of each service, so a jump from a trace to its logs works at once. Loading again adds data
for the current time. Loading requires `streams.write`.

## System health and priority streams

**System health overview** charts the period by **Raw intake**, **Compressed**, or **Events**, and
lists the state of each signal type. When a source stopped sending, the chart says so and offers
**Check data intake**.

**Priority streams** lists the streams that need attention first, with the type, the state, the
intake rate, and the last time data arrived. Select a stream to open it in its explorer, or
**View all** to open [Streams](https://docs.molesignal.com/en-US/streams.md).

| State | Meaning |
| - | - |
| **Healthy** | Data arrived in the last 15 minutes. |
| **Delayed** | The last data arrived between 15 minutes and 2 hours ago. |
| **Interrupted** | No data for 2 to 24 hours. |
| **Stale** | No data for more than 24 hours. |
| **No data** | The stream has never received data, or it is the stream of Mole Agent traces, which is quiet between answers. |

## On-call, activity, and dashboards

The column on the right follows the [on-call schedules](https://docs.molesignal.com/en-US/alerting/on-call.md):

* **My on-call** while the signed-in user is on call, otherwise **On call now** for a schedule of
  the workspace, with the progress of the shift, the next handoff, and the escalation policies.
* The shift figures: the incidents of the shift, how many wait for acknowledgement, and how many
  were acknowledged or escalated.
* A temporary override names the person who covers and until when.
* **On-call coverage gap** appears when nobody is on call. **Assign now** opens the schedule to add
  a temporary override.

**Recent activity** lists the latest changes to dashboards, alerts, pipelines, and other resources
from the audit trail. **View all** opens **Settings → Audit**.

**Recent dashboards** lists the dashboards changed last, with their panel counts. **Add panels**
opens the panel editor of a dashboard that has none.

## Permissions

Each part loads with the read permission of its area.

| Permission | Part |
| - | - |
| `streams.read` | Intake verdict and priority streams. |
| `streams.query` | Raw intake volume, compressed size, and the health chart. |
| `alerts.read` | Critical banner and active alerts. |
| `schedules.read` | On-call. |
| `audit.read` | Recent activity. |
| `dashboards.read` | Recent dashboards. |
| `streams.write` | **Load** in the quick start. |


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