Codefresh offers several metrics for pipeline steps that allow you to get a better overview on the resources

Codefresh offers several metrics for the pipeline, and for steps in the pipeline, that allow you to get a better overview of the resources

consumed by your pipeline.

At the most basic level Codefresh will show some quick metrics while the pipeline is running that include

**Pipeline metrics**

At the most basic level, Codefresh displays quick metrics while the pipeline is running that include

memory consumed and size of logs:

{% include

image.html

lightbox="true"

file="/images/pipeline/monitoring/quick-pipeline-metrics.png"

url="/images/pipeline/monitoring/quick-pipeline-metrics.png"

alt="Pipelinerunningmetrics"

caption="Pipelinerunningmetrics"

max-width="70%"

alt="Metrics forrunningpipeline"

caption="Metrics forrunningpipeline"

max-width="95%"

%}

You can then get the memory usage for the whole pipeline by clicking on the metrics tab at the bottom of the screen.

* To view memory and disk usage for running or completed pipeline builds, click the**Metrics** tab at the bottom of the Build page.

* Memory usage: View memory usage (Y-axis) by time (X-axis) for the duration of the build.

* Disk usage: View disk usage (Y-axis) by time (X-axis) for the duration of the build. The red line is set at 90% of the maximum disk space.

To see the precise usage at different points in time, mouse over the dots.

Viewing the actual disk usage for a build during its run allows you to better gauge and define the[minimum disk space required for the build volume]({{site.baseurl}}/docs/pipelines/pipelines/#runtime).

{% include

image.html

lightbox="true"

file="/images/pipeline/monitoring/pipeline-metrics.png"

url="/images/pipeline/monitoring/pipeline-metrics.png"

alt="Pipeline detailedmetrics"

caption="Pipeline detailedmetrics"

max-width="70%"

alt="Detailedmetrics for pipelines"

caption="Detailedmetrics for pipelines"

max-width="60%"

%}

If you click on an individual step before clicking the*Metrics* tab you will get metrics for that specific step only.

**Pipeline-step metrics**

For step-specific metrics, first select the step, and then click the**Metrics** tab.

Step metrics are available for memory and CPU usage (not disk space).

{% include

%}

You can choose to restart any pipeline by clicking the button at the top right corner.

- Medium (recommended 3-4 steps)

- Large (recommended 5-6 steps)

Set the disk space you need for the pipeline's build volume. Configuring the disk space per pipeline build volume prevents out-of-space scenarios that lead to failed builds. The disk space set for the pipeline is inherited by all the builds run for the pipeline.

To speed up builds and improve performance, Codefresh caches different types of data during pipeline execution for reuse across builds. Image-caching is one example of cached data, where Codefresh pulls the required images during the first build and caches them for reuse in future builds. For more info, see[Pipeline caching]({{site.baseurl}}docs/configure-ci-cd-pipeline/pipeline-caching).

Because a portion of the disk space is already utilized by cache, a build can run out of disk space and fail with the 'no space left on device' error.

Codefresh calculates the available range according tothe disk size, and automatically sets the disk space for the build volume to 70% ofthetotal disk space. You caneitherretain the default allocationorchange as needed.

To prevent out-of-space scenarios that lead tofailed builds, you can set theminimumdisk spaceyou needfor thepipeline'sbuild volume. Definingtheminimum disk space ensures that Codefresh assignseithera cached disk with sufficient disk spaceora new empty disk at the start of the build.

The disk space set for the pipeline is inherited by all the builds run for the pipeline.

You can also configure the disk space for a[specific trigger]({{site.baseurl}}/docs/configure-ci-cd-pipeline/triggers/git-triggers/#set-minimum-disk-space-for-build-volume-by-trigger) used by the pipeline or for a specific run, and override what's set for the pipeline.

1. Select the pipeline for which to set the disk space.

1. Select the pipeline for which to set theminimumdisk space.

1. Select**Settings**, and then**Runtime**.

1. Enable**Set minimum required disk space** and either retain the default displayed or change as needed.

1. Enable**Set minimum required disk space**, and either retain the default displayed or change as needed.

{% include

image.html