Insights metric chart reference

Metric charts can be attached to dashboards, value streams, and applications in the Portfolio view.

HCL DevOps Velocity (Velocity) provides metric definitions that you can apply to value streams, deployments, pipelines, and applications. Metric definitions describe expected data types and default chart settings. You can also send custom metric definitions to Velocity from the external clients by using the API.

Metric definitions, when applied to data, are represented by charts and graphs that can be attached to dashboards, value streams, and applications in the Portfolio view. Depending on how the data is collected, metric charts can be updated in near-real-time.

Velocity provides many pre-defined metric definitions and their related charts. You can create your own custom metric definitions and use them wherever you would use a pre-defined one.

Delivery flow charts

Table 1. Delivery flow-type charts
Chart Description
Lead Time The time required for a dot to go from business acceptance to value realization. This includes both engineering time and non-value-added waiting time between sub-processes.
Lead Time Key Performance Indicator (KPI) The Lead Time KPI measures the efficiency of a dot to reach the defined target. You can define the target using the status rule. To define target for lead time KPI, see here.
Cycle Time This is similar to lead time, except cycle time is measured from when the development team begins work to when that work reaches the customer.
Cycle Time Key Performance Indicator (KPI) The Cycle Time KPI measures the efficiency of a dot to reach the defined target. You can define the target using the status rule. To define target for cycle time KPI, see here.
Dev Cycle Time This is similar to cycle time, except dev-cycle time is measured from when the development team begins work to when that work reaches end of the development (before the production stage).
Build Counts Number of builds by type in a specified time period.
Deployment Counts Number of deploys by status in a specified time period. The metric can be set to process names, environment, result, type, or application. The default metric is result. The data can scoped by data set, environment, process, result, or version.
Load The number of work items active or waiting in a value stream at a given time. Load measures utilization capabilities of value streams related to productivity in the process flow. "Active" refers to the stages from the lead-time start until the lead-time end.
Throughput The rate of work items completed during a period of time. Improving throughput can result in better responsiveness to customer requirements and may yield lead time reductions for value streams.
Distribution The proportion of different types of work items over time. This provides teams visibility into the type of work being completed (features, defects, tasks, and so forth.)
P.R.E Risk Probabilistic Risk Estimator (P.R.E) Risk provides estimated probability to miss current sprint goal.
P.R.E Deadline P.R.E Deadline provides estimated complete date for the current sprint.

DevOps Research and Assessment (DORA) metrics

Table 2. DORA charts
Chart Description
Deployment Frequency The number deployments into production environment.
Lead Time to Change The time required for a dot to go from commit to production deployment.
Time To Restore Service (MTTR) The time taken to resolve the incident.

Cycle Time KPI

To add Cycle Time KPI chart to dashboard, complete the following steps:
  1. On the navigation bar, click Insights.
  2. Select the required dashboard.
  3. Under the dashboard, click Add charts.
  4. Click right angle bracket to expand the Delivery Flow chart list.
  5. Click Add + for Cycle Time KPI to add the chart to the dashboard.
  6. The Cycle Time KPI chart is displayed with the following default status rule:
    Table 3. Cycle Time KPI
    Status rule range Color
    0-5 Green
    5-10 Yellow
    10-30 Red
    Note: The default status rule can be customized as required. See custom status rule for cycle time KPI.
To set custom status rule for cycle time KPI, complete the following steps:
  1. On the Home page, click Settings on upper-right corner of the page.
  2. Click Insights > KPIs.
  3. To set the status rule for Cycle Time KPI, click an overflow menu and select Edit. The Edit KPI Definition - Cycle Time KPI. window is displayed.
  4. In Edit KPI Definition - Cycle Time KPI. window, click Add status rule to add a status rule.
  5. In Rule name field, enter the name for the rule.
  6. In Rule section in Edit KPI Definition - Cycle Time KPI., select the range and color for the rule status.
  7. Click Add row to add range for custom status rules. You can select the color for each range of custom status rule.
    Note: You can add, edit, and delete status rules.
  8. In Scope > Teams field, select the teams to apply the status rule.
  9. In Scope > Value streams field, select the value stream to apply the status rule.
  10. In Scope > Applications field, select the application to apply the status rule.
  11. Click Confirm.
  12. Click Submit.

Lead Time KPI

To add Lead Time KPI chart to dashboard, complete the following steps:
  1. On the navigation bar, click Insights.
  2. Select the required dashboard.
  3. Under the dashboard, click Add charts.
  4. Click right angle bracket to expand the Delivery Flow chart list.
  5. Click Add + for Lead Time KPI to add the chart to dashboard.
  6. The Lead Time KPI chart is displayed with the following default status rule:
    Table 4. Lead Time KPI
    Status rule range Color
    0-5 Green
    5-10 Yellow
    10-30 Red
    Note: The default status rule can be customized as required. See custom status rule for cycle time KPI.
To set the status rule for lead time KPI, complete the following steps:
  1. On the Home page, click Settings on upper-right corner of the page.
  2. Click Insights > KPIs.
  3. To set the status rule for Lead Time KPI, click an overflow menu and select Edit. The Edit KPI Definition - Lead Time KPI. window is displayed.
  4. In Edit KPI Definition - Lead Time KPI. window, click Add status rule to add a status rule.
  5. In Rule name field, enter the name for the rule.
  6. In Rule section in Edit KPI Definition - Lead Time KPI., select the range and colour for the rule status.
  7. Click Add row to add range for custom status rules. You can select the color for each range of custom status rule.
    Note: You can add, edit, and delete status rule.
  8. In Scope > Teams field, select the teams to apply the status rule.
  9. In Scope > Value streams field, select the value stream to apply the status rule.
  10. In Scope > Applications field, select the application to apply the status rule.
  11. Click Confirm.
  12. Click Submit.

Quality charts

Table 5. Quality-type charts
Chart Description
Coverage By Branch Percent of branches with associated tests executed during testing.
Coverage By Function Percent of program functions executed during testing.
Coverage By Line Percent of lines of code executed during testing.
Functional Tests Number of functional tests by status in a specified period of time.
Static Code Analysis Number of issues by severity in a specified period of time.
Unit Tests Number of tests by status in a specified period of time.

Risk charts

Table 6. Risk-type charts
Chart Description
Container Vulnerabilities Number of container vulnerabilities by severity in a specified period of time. The metric can be set to process names, environment, result, type, application, tag, or team. The default metric is result. The data can scoped by data set, process, or version.
Application Vulnerabilities Number of application vulnerabilities by severity in a specified period of time.