Insights metric chart reference#
Metric charts can be attached to dashboards, value streams, and applications in the Portfolio view.
HCL™ Accelerate 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 HCL Accelerate 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.
HCL Accelerate 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#
|Lead Time||The time required for a dot to go from business accepted to value realization. This includes both engineering time and non-value-added waiting time between sub-processes.|
|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.|
|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.)|
|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.|
|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.|
- Lead- and cycle-time table metrics
Lead and cycle time table metrics provide refined granularity for issues.
Parent topic: Managing Insights dashboards