> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/features-new-ui/devices/fleet-overview.md).
# Fleet Overview
The Overview page is the dashboard for your JFrog Connect fleet. You can see top level information such as fleet stats, latest device registrations, and distribution of your fleet and deployments.
## Dashboard View
The Overview page provides a dashboard view of your fleet or of any subset of your fleet that you filter. To see the dashboard view, go to Overview at the top of the left navigation tree.
### Fleet
The Overview page shows information per fleet. If you have multiple fleets in your account, you can choose the displayed fleet in the dropdown at the top of the page.
### Filter
In the Overview dashboard you can display a subset of the fleet according to any filter you set. To [filter devices](/features-new-ui/devices/fleet-overview/filter-bar.md) in the dashboard, click the funnel icon on the top right of the page.
### Notifications
Click the bell in the upper right corner to see system notifications. A red circle on the bell indicates that you have new notifications since the last time you checked. Labels on the notifications indicate the notification type, for example, General, Updates, or Devices, and the severity, for example, Info, Error, or Warning.
### Overview Panels
The panels on the overview page show different types of information.
* **Devices**: Shows number of devices online, offline, and total in the filter chosen. Click one of the tiles to show the list of devices.
* **Ongoing Alerts**: Shows the number of ongoing alerts for resources and processes.
* **Device Registrations**: The [Device Registration](https://docs.connect.jfrog.io/get-to-know-new-ui/get-started/register-device-agent-7.0) panel has a chart showing the number of devices registered to this fleet in the last few months.
* **Device Security Risks**: Shows the number of devices at each risk level. (Appears in Enterprise accounts only.)
* **Deployment Tag Distribution**: You can choose a deployment tag from the list and view a circle chart breakdown of the number of devices with that tag, per version of the tag.
* **Device Fleet Map**: The map is useful to get a graphic overview of your device distribution and where devices are online or offline. If you click on a device location, a tooltip will open with more information about the device. You can also use the map to find the exact location of a device. Just enter the device name in the search box. You can adjust the position and magnification of the map as needed. For more information about the map and device location, see [Locate Devices](/features-new-ui/devices/fleet-overview/map.md).
## What’s Next?
Learn how to [filter the devices](/features-new-ui/devices/fleet-overview/filter-bar.md) you see in the Overview page.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.connect.jfrog.io/features-new-ui/devices/fleet-overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
