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

# Activity

> Monitor pipeline runs, traces, and system events

The Activity page shows a timeline of all sessions, pipeline executions, and system events in your workspace.

## Sessions

A **Sessions** section appears above the pipeline run timeline and lists agent sessions from the last 30 days. Each session entry shows:

* **Status** — Color-coded indicator: green for completed, amber for abandoned, red for failed or with errors.
* **Label** — Session ID or a descriptive label if one is set.
* **Model** — The last model used during the session.
* **Tokens** — Combined input and output token count.
* **Errors** — Number of errors recorded in the session.
* **Last activity** — Time of the most recent event in the session.

Click a session to expand it and view its **trace steps**: a numbered list of internal function calls with their status, return value snippet, and timestamp.

### Deep-linking to a session

Append `?session=<session_id>` to the Activity page URL to automatically expand and scroll to that session on load.

## Activity timeline

Events are grouped by date. Each entry shows:

* **Operation** — The pipeline or action that ran (e.g., cognify, add, search).
* **Status** — `Completed`, `Started`, or `Error`.
* **Owner** — The user or agent that triggered the operation.
* **Dataset** — The dataset involved.
* **Timestamp** — When the event occurred.

Use the filters at the top to narrow by **agent** or **dataset**. The header shows the total count of both events and sessions currently loaded.

## Trace viewer

Click a completed pipeline run to expand its trace. The trace shows individual spans grouped by category:

* **LLM** — Language model calls (entity extraction, summarization).
* **Vector** — Embedding generation and vector store operations.
* **Graph** — Knowledge graph write and query operations.
* **Search** — Retrieval operations.
* **System** — Internal orchestration steps.

Each span includes its duration, which helps identify bottlenecks in processing.

## Pagination

The pipeline run timeline loads 10 events at a time. Use the **Previous** and **Next** buttons at the bottom to navigate between pages.