You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/dashboards/home-dashboard.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -255,7 +255,7 @@ Use the Pipelines dashboard to:
255
255
Filters narrow the scope of aggregated data, allowing you to focus on the information you want to see.
256
256
Unless otherwise indicated, all filters support multi-selection.
257
257
258
-
>**TIP**:
258
+
>**TIP**:
259
259
Different filter types have an AND relationship.
260
260
261
261
@@ -264,7 +264,7 @@ Different filter types have an AND relationship.
264
264
| -------------- | --------------|
265
265
|**Date Range**| The time frame for which to view data. The date range affects the other filters, including the granularity for the Success Rate and Pipeline Duration charts. <br>In addition to the predefined date ranges, you can select a custom date range of up to the last six months. <br>If you select Today, then the Success Rate and Duration charts reflect hourly granularity.<br><br>Every date range you select has a reference period corresponding to the same period of time preceding the selected date range. The reference period is used to derive comparisons and identify trends. |
266
266
| **Hourly/Daily** |Based on the date range selected, choose the granularity for viewing Success Rate and Pipeline Duration. {::nomarkdown}<ul><li>A date range between 1 and 4 days allows viewing metrics either by hour or by day.</li><li>A date range longer than four days allows viewing metrics only by day. The Hourly option is disabled in this case.</li></ul> {:/}
267
-
|**Project**| The project or projects to which the pipeline belongs.Selecting a project allows you to focus on performance of pipelines assigned to it. If you starred one or more projects as favorites and selected projects, clicking {::nomarkdown}<imgsrc="../../../images/icons/icon-fav-starred.png?display=inline-block">{:/}, filters pipelines by the selected projects.|
267
+
|**Project**| The project or projects to which the pipeline belongs.<br>Selecting a project allows you to focus on the performance of pipelines assigned to it. If you starred one or more projects as favorites, and selected Projects, clicking {::nomarkdown}<imgsrc="../../../images/icons/icon-fav-starred.png?display=inline-block">{:/}, filters pipelines by the selected projects.|
268
268
|**Pipeline**| The pipeline or pipelines to filter by. <br>Mouse over a pipeline name in the list displays a tooltip including the name of the project to which the pipeline belongs, followed by the name of the pipeline, to easily identify and select the correct pipeline.<br>If you starred one or more pipelines as favorites, clicking {::nomarkdown}<imgsrc="../../../images/icons/icon-fav-starred.png?display=inline-block">{:/}, filters by those pipelines. |
269
269
|**Status**| {::nomarkdown}<ul><li><b>Error</b>: Pipelines with builds that failed due to errors in the pipeline specifications or steps that failed. </li><li><b>Succeeded</b>: Pipelines with builds that completed successfully.</li> <li><b>Terminated</b>: Pipelines with builds terminated by the system according to the policy defined in the pipeline's settings. These can be any of these: <ul><li>Recent build from the same branch terminating all previous pipeline builds </li><li>Recent build from the specified branch terminating all previous builds from that branch</li><li>Running build terminating all running builds</li><li>Child builds terminated when the parent build is terminated.</li> </ul></li>For details, see <ahref ="https://codefresh.io/docs/docs/pipelines/pipelines/#policies">Build Termination in Pipeline Policies</a>. </ul>{:/}|
270
270
|**Tags**|The tag or tags assigned to the pipelines. |
@@ -274,7 +274,7 @@ Different filter types have an AND relationship.
274
274
275
275
### Pipeline success rate
276
276
The pipelines that completed execution successfully, from the total number of pipelines executed within the selected date range, as percentage.
277
-
> TIP:
277
+
> **TIP**:
278
278
Pipelines in Pending status are excluded from the Success Rate calculations.
279
279
280
280
@@ -287,12 +287,12 @@ You can switch between average (the default), and percentile views.
287
287
The average duration calculation shows the duration across all the pipelines within the selected date range.
288
288
To better understand the performance over time, switch to duration by the median (P-50) or the 90th (P-90) percentiles.
289
289
290
-
The comparison percentage is derived from the reference time period. The reference period corresponds to the same length of time that preceding the date range selected. <br>
290
+
The comparison percentage is derived from the reference time period. The reference period corresponds to the same length of time that precedes selected the date range. <br>
291
291
292
292
**Pipeline duration breakdown**
293
-
Every pipeline workflow can be divided into phases, some of which apply to all pipelines, while others depend on the settings configured for each pipeline. The initialization phase is common to all pipelines. Other phases such as pending approval to continue execution, and pending execution due to concurrency limits depends on the settings.
293
+
The workflow of every pipeline can be divided into phases, some of which apply to all pipelines, while others depend on the settings configured for each pipeline. The initialization phase in the workflow is common to all pipelines. Other phases such as pending approval to continue execution, and pending execution due to concurrency limits, depend on the settings configured for each pipeline.
294
294
295
-
>TIP:
295
+
>**TIP**:
296
296
Each phase is color-coded for easy visualization. To show/hide phases in the chart, click the name of the phase in the legend.
297
297
298
298
{% include image.html
@@ -315,7 +315,9 @@ Every pipeline workflow can be divided into phases, some of which apply to all p
315
315
316
316
***Pending concurrency policy**
317
317
The average duration of pipeline workflows pending execution due to the concurrency limits configured for the pipelines. Workflows with pipeline, trigger, and branch concurrency limits are included in the calculation.
318
-
>Pipeline workflows pending execution due to concurrency policies are affected by the global account or pipeline's settings for Pending approval.
318
+
319
+
>**TIP**:
320
+
Pipeline workflows pending execution due to concurrency policies are affected by the global account settings or the pipeline's settings for Pending approval.
319
321
320
322
***Delayed due to license limit**
321
323
The pipeline workflows pending execution due to the license limits configured for your account.
0 commit comments