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

# Ozone Dashboard

Ozone offers the most simplest and meaningful dashboard available on a DevOps platform. Usually, widgets, windows, and tabs would need to be added into the dashboard under the pretext of “customization”, until which no information would be displayed.

However, Ozone dashboard is the first screen that would be visible with meaningful insights to users as soon as they login and covers the following:

1. Project setup
2. DORA
3. Deployments
4. Cluster insights
5. Microservices overview
6. Pipeline and task runs

Based on the project that is selected, the dashboard has a widget that shows the project completion status along with setup tasks that are pending to be completed.

<figure><img src="/files/q4cFHZsViqwuw4yZ1GGM" alt=""><figcaption></figcaption></figure>

A snapshot of total number of deployments, rollbacks, failure rates, and commits/pull requests are mentioned in the top row. Below, detailed DORA metrics are visually represented.

Filters for deployments, microservices, and clusters enable users to view specific project insights.

Toggling to “Deployments” updates the screen to give you a detailed real-time overview of all your deployments.

<figure><img src="/files/1EZC7ldysCDvb0Mrq1gh" alt=""><figcaption></figcaption></figure>

A set of filters lets you select between deployments, runtime, clusters, status, and namespace for accurate reporting. A snapshot in the form of total deployments is mentioned in the top row followed by the live pipeline status and the related visuals below.


---

# 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.ozone.one/ozone-end-user-guide/documentation/dashboard/ozone-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.