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

# Dashboard

The Overview workspace summarizes live network health, inventory changes, and device activity.

## Who Can Access It

Any authenticated user can open Overview.

## When To Use It

Use Overview as the first stop after signing in. It is intended to answer:

* is the network healthy right now?
* how many devices are known?
* are there monitoring changes or incidents to investigate?
* did recent inventory/discovery activity change the state of the network?

## Data Sources

The workspace uses dashboard and monitoring summary data:

* `GET /api/v1/dashboard/summary`
* `GET /api/v1/monitoring/summary`

## What To Check

Review:

* fleet health;
* device counts;
* recent activity;
* monitoring summaries;
* changes that should be followed up in Inventory, Topology, Monitoring, Security, or IPAM.

## API Equivalent

```bash
API_URL="https://netmap.example.com"
API_KEY="<api-key>"

curl --fail-with-body \
  --url "${API_URL}/api/v1/dashboard/summary" \
  --header "X-API-Key: ${API_KEY}"
```

## Common Problems

| Symptom                      | Likely cause                   | Fix                                      |
| ---------------------------- | ------------------------------ | ---------------------------------------- |
| Overview does not load       | unauthenticated session        | sign in again                            |
| Monitoring counts look stale | background refresh in progress | open Monitoring for detailed device rows |
| API returns `401`            | missing/invalid auth           | check token or API key                   |

## Related Pages

* [Monitoring](/using-netmap/monitoring.md)
* [Inventory](/using-netmap/inventory.md)
* [API Authentication](/api/authentication.md)


---

# 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.netmap.dev/using-netmap/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.