Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Update monitoring-pipelines.md#528

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
NimRegev merged 8 commits intomasterfromclassic-disk-space-graph
Dec 22, 2022
Merged
Show file tree
Hide file tree
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 21 additions & 10 deletions_docs/configure-ci-cd-pipeline/monitoring-pipelines.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -312,36 +312,47 @@ In both cases you can copy to clipboard the yaml shown using the button at the t

### Viewing pipeline metrics

Codefresh offers several metrics for pipelinesteps that allow you to get a better overviewon the resources
Codefresh offers several metrics forthepipeline, and forstepsin the pipeline,that allow you to get a better overviewof 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/configure-ci-cd-pipeline/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
Expand Down
Binary file modifiedimages/pipeline/monitoring/pipeline-metrics.png
View file
Open in desktop
Loading
Sorry, something went wrong.Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

[8]ページ先頭

©2009-2025 Movatter.jp