# Code to Cloud Dashboard **Code to Cloud Dashboard** When you open Code to Cloud from the left sidebar in the Opsera portal, you land on the main pipeline dashboard. The dashboard has three tabs: * **Pipelines** — live status of all your C2C pipelines across all organizations * **Activity** — a chronological log of all pipeline events across your organization * **Templates** — pre-built pipeline templates ## **The Pipeline Dashboard** **1. Top Stats — At a Glance** The four cards at the top of the dashboard give you an instant snapshot of your deployment fleet: | Card | What it Shows | | ----------------- | ------------------------------------------------------------------------ | | **C2C Pipelines** | Total number of Code to Cloud pipelines configured, with total run count | | **Deployed** | Pipelines with a live running application, with success rate percentage | | **Active Runs** | Pipelines currently executing, with count of runs in a waiting state | | **Failed** | Pipelines that need attention — runs that did not complete successfully | **2. The Pipeline List** Below the stats, the pipeline list shows every C2C pipeline you have access to, with the total pipeline count displayed next to the **C2C Pipelines** label. Each row shows: | Column | Description | | ---------------- | -------------------------------------------------------------------------------------------------------------- | | **Pipeline** | Pipeline name and branch. A coloured left border indicates last run status — red for failed, green for success | | **Owner** | The user who created the pipeline and their email | | **Organization** | The Opsera organization the pipeline belongs to | | **Repository** | The linked source control repository | | **Environment** | The target environment shown as a badge — DEV, TEST, UAT, or PROD | | **Last Run** | Status of the most recent run (Failed / Success), run count, a visual run history bar, and time since last run | | **Actions** | **Run** button to trigger the pipeline manually, and a delete option | **3. Filtering and Navigation** Use the filter bar to narrow the pipeline list by: * **Search** — Type a pipeline name to find it instantly * **All Status** — Filter by run status: All Status / Running / Success / Failed * **All Envs** — Filter by environment: All Envs / dev / test / uat / prod * **All Orgs** — Filter by organization * **Refresh** — Manually refresh the list to pick up the latest run status ## **Individual Pipeline View** Clicking into any pipeline opens the pipeline detail page. At the top, the pipeline header shows the pipeline name, environment badge, branch, and the **Run Pipeline** button. **Pipeline Stats** Four cards show pipeline-level metrics: | Card | What it Shows | | ---------------- | ------------------------------------------------------ | | **Total Runs** | Number of runs executed, with passed and failed counts | | **Success Rate** | Percentage of runs that completed successfully | | **Avg Duration** | Average time per pipeline run | | **Last Run** | Time since the most recent run | **Stage Visualisation** The pipeline canvas shows the full stage chain for your pipeline — for example `Clone → Code Scan → Docker Build → Image Scan → Push → Deploy`. Each stage card shows its name and last run status. A red border and failed indicator appears on stages that did not complete successfully. **Pipeline Tabs** | Tab | What it Shows | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | **Runs** | Full run history. Each run shows its number, status, stage-level indicators, timestamp, and any error message. Expand a run to see per-stage detail | | **Deployment Plan** | Environment configuration, ingress host, namespace, trigger settings, and stack configuration | | **Webhook** | Configure automatic pipeline triggering on git push | | **Variables** | All pipeline variables — pre-filled and secrets — with edit access | | **Blueprint** | The generated pipeline script. A blue dot indicates the script is present | | **Activity** | Timestamped log of all events for this specific pipeline | | **Logs** | Raw execution logs for the most recent run | **Run History** Each entry in the Runs tab shows the run number, overall status, individual stage indicators, timestamp, and — if the run failed — the specific error message --- # 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/code-to-cloud/code-to-cloud-dashboard.md?ask= ``` 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.