# Vibe-Shift Dashboard

<figure><img src="/files/7QqjmDw35WKmT1khMDRL" alt=""><figcaption></figcaption></figure>

When you open Vibe-Shift from the left sidebar, you land on the main pipeline dashboard. There are two primary views available:

* **Pipeline Dashboard** — live status of all your pipelines across all organisations
* **Insights View** — high-level analytics and trends, accessed via the View Insights button

## The Pipeline Dashboard

{% stepper %}
{% step %}

### **Top Stats — At a Glance**

The four cards at the top of the dashboard give you an instant snapshot of your deployment fleet:

<table><thead><tr><th width="167.65203857421875">Card</th><th>What it shows</th></tr></thead><tbody><tr><td><strong>VS Pipelines</strong></td><td>Total number of VIBEshift pipelines configured </td></tr><tr><td><strong>Deployed</strong></td><td>Pipelines with a live running app </td></tr><tr><td><strong>Healthy</strong></td><td>Pipelines passing health checks </td></tr><tr><td><strong>Active Runs</strong></td><td>Pipelines currently in progress</td></tr></tbody></table>
{% endstep %}

{% step %}

### **The Pipeline List**

Below the stats cards is your full pipeline list. Each row shows:

* **Pipeline name** — with branch (`main`) and GitOps/auto-deploy indicators
* **Owner** — name and email of the pipeline creator
* **Organisation** — which org the pipeline belongs to
* **Repository** — the connected GitHub/GitLab/Bitbucket repo
* **Environment** — `DEV` or `PROD` badge
* **Deployment** — live health status (Healthy / Unknown)
* **Last Run** — status badge (Success / Cancelled / No runs) and time elapsed

> **Note:** A Cancelled status on an older run does not affect the current deployment health. The pipeline still shows Healthy if the most recent successful run deployed correctly.
> {% endstep %}

{% step %}

### **Filtering and Navigation**

Use the controls above the pipeline list to narrow your view:

* **Search** — search pipelines by name
* **All Status** — filter by Success, Failed, Running, or Cancelled
* **All Envs** — filter to show only DEV or PROD pipelines
* **All Organizations** — scope the list to a specific org
* **Refresh** — force-refresh all pipeline statuses
* **+ New Vibe-Shift Pipeline** — create a new pipeline (top right)
  {% endstep %}
  {% endstepper %}

## The Insights Dashboard

Click **View Insights** from the main dashboard to open the analytics view, scoped across all organisations.

{% stepper %}
{% step %}

### **Top Metrics**

Four summary cards give you the organisation-wide health picture:

| Metric           |
| ---------------- |
| **Pipelines**    |
| **Total Runs**   |
| **Success Rate** |
| **Deployed**     |
| {% endstep %}    |

{% step %}

### **Pipelines by Environment**

A donut chart showing how your pipelines are distributed across environments:

* **dev** — 6 pipelines
* **prod** — 1 pipeline

Use this to understand whether your team is primarily working in dev or moving workloads into production.
{% endstep %}

{% step %}

### **Run Activity (Last 30 Days)**

A line graph tracking success vs failed runs
{% endstep %}

{% step %}

### **Organizations Tab**

A per-organisation breakdown of pipeline health. Currently showing 2 organisations:
{% endstep %}

{% step %}

### **Users Tab**

Switch to the **Users** tab to see activity broken down per developer — pipelines owned, total runs, success and failure counts, average run duration, and last run timestamp.
{% endstep %}

{% step %}

### **Activity Tab**

Switch to the **Activity** tab for a run-by-run environment breakdown, showing which environments are being exercised and at what frequency.
{% endstep %}
{% endstepper %}


---

# Agent Instructions: 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:

```
GET https://docs.agents.opsera.ai/vibe-shift/vibe-shift-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.