> ## Documentation Index
> Fetch the complete documentation index at: https://namespace.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Builds UI
export const CenteredImage = ({src, alt, width, caption, className}) => {
const [basePath, setBasePath] = useState("");
useEffect(() => {
const path = window.location.pathname;
setBasePath(path === "/docs" || path.startsWith("/docs/") ? "/docs" : "");
}, []);
return
;
};
## Overview
The Build Dashboard provides comprehensive insights into your build performance and failures through detailed traces, step logs, and contextual information.
This centralized view helps you quickly identify, debug, and optimize your Docker builds.
## Build Failure Analysis
**Failure Detection & Highlighting**
The dashboard automatically extracts and highlights build failure causes directly in the main view. Failed builds are prominently displayed with clear error indicators and quick access to detailed diagnostics.
**Step-by-Step Logs**
Navigate to the logs view to examine detailed output for each build step. This granular visibility allows you to understand the exact context and sequence of events leading to failures.
**Build Attribution**
Each build failure includes contextual information showing the specific commit used as the build base and the build machine that executed the build.
This attribution data is essential for determining whether failures stem from recent code changes or infrastructure issues.
## Performance Monitoring
**Cache Utilization Overview**
The dashboard provides at-a-glance visibility into which build steps utilized cache effectively. Cached steps are clearly marked, helping you identify unexpected cache misses that may indicate suboptimal build definitions.
**Critical Path Analysis**
The build trace view visualizes your build execution's critical path, highlighting bottlenecks and parallel execution opportunities.
## Builds in Context
**Integrated Workflow Attribution**
When builds are initiated from Namespace compute environments, the dashboard records and displays these connections, enabling you to trace builds back to their originating workflows.
**Bidirectional Navigation**
The connection tracking works both ways - from the dashboard, you can navigate to associated GitHub Actions runs, and from GitHub Actions debugging views, you can inspect related builds with a single click.