Understanding analytics in CloudBees Unify

CloudBees Unify analytics operate through integrated data collection from workflows, external tool integrations, and platform operations, with each data source contributing to multiple dashboard views.

Workflow runs provide foundational execution data that feeds into multiple analytics frameworks simultaneously. When you annotate workflow steps with kind: build or kind: deploy, this metadata enables CloudBees Unify to automatically categorize execution data for DORA metrics, software delivery activity tracking, and deployment analysis. The same workflow run can contribute test results to test insights, security scan results to security insights, and deployment data to DORA calculations.

External integrations extend analytics data collection beyond platform boundaries through CloudBees Unify’s integration architecture. Jira integrations enable flow metrics by connecting issue lifecycle data with commit and deployment activities tracked in workflows. Jenkins and CloudBees CI integrations provide build execution data for CI insights dashboards. Source code management integrations contribute commit patterns and pull request data that appear across software delivery activity and development cycle analysis.

This integrated architecture ensures comprehensive performance visibility because CloudBees Unify correlates data across organizational boundaries through its component and environment model. A single deployment affects multiple analytics views: DORA deployment frequency, environment-specific activity tracking, component-level performance trends, and security posture analysis if scanning occurs.

CloudBees Unify implements DORA metrics by analyzing workflow execution patterns and correlating them with deployment outcomes across your configured components and environments.

Deployment frequency calculation relies on workflow runs marked with kind: deploy step annotations. CloudBees Unify counts successful deployments per component and environment within specified time windows, enabling DORA analysis at organizational, team, or application levels. This implementation accounts for CloudBees Unify’s multi-tenant architecture where different teams deploy to different environments at different cadences.

Lead time measurement tracks duration from commit to successful deployment by correlating git commit timestamps with workflow completion times. CloudBees Unify connects source code management integrations with workflow execution data to calculate accurate lead times across complex delivery pipelines. The platform’s component model ensures lead time calculations account for dependencies and multi-service deployments.

Change failure rate emerges from CloudBees Unify’s correlation of deployment activities with subsequent failure indicators. The platform identifies failures through workflow run failures, environment health checks, and rollback patterns detected across integrated monitoring tools. Mean time to recovery calculations track duration between failure detection and successful recovery deployment, leveraging the same workflow execution data.

This implementation provides DORA measurement that reflects CloudBees Unify’s specific architectural patterns: component-based organization, environment-centric deployments, and workflow-driven automation. Organizations using external CI/CD tools achieve DORA measurement by integrating those tools with CloudBees Unify and ensuring proper workflow metadata annotation.

CloudBees Unify enables flow metrics through its analytics configuration system that connects Jira work item lifecycle data with development execution data captured across workflows and integrations.

Flow metrics require explicit configuration where you map Jira issue types to flow item categories (features, defects, risk, technical debt) within CloudBees Unify’s analytics configuration. This mapping enables the platform to track work progression from Jira issue creation through completion while correlating with development activities captured in workflow runs and commit patterns. The correlation works because CloudBees Unify matches Jira issue keys in commit messages with workflow execution data.

Cycle time calculation measures duration between Jira issue status transitions that you configure as "start" and "done" states for each project. CloudBees Unify tracks these transitions through its Jira integration and correlates them with development activity to provide accurate cycle time measurement across complex multi-team scenarios. Efficiency metrics separate active work time from wait time using your status mapping configuration to distinguish between development states and approval, review, or blocked conditions.

Velocity and workload calculations aggregate work item completion and in-progress counts across configured time windows and component boundaries. Work items distribution analysis uses your flow item type mapping to reveal how organizational capacity allocates between new features, technical debt, defect resolution, and risk mitigation.

This implementation makes flow metrics dependent on both Jira integration quality and analytics configuration accuracy within CloudBees Unify. Inconsistent Jira usage patterns or incomplete status transition data directly affect flow metrics reliability, which is why the platform provides configuration validation and data quality indicators.

CloudBees Unify provides operational analytics through CI insights, software delivery activity, test insights, and security insights that reveal platform health patterns and correlate with higher-level performance metrics through the platform’s unified data model.

CI insights analyze data from Jenkins and CloudBees CI integrations to reveal build infrastructure utilization, queue patterns, and system health indicators within your CloudBees Unify environment. This operational data explains DORA metric variations by surfacing infrastructure constraints that affect deployment frequency or build reliability issues that impact change failure rates across your configured components.

Software delivery activity tracking aggregates commit patterns, pull request workflows, and build execution statistics from source code management and CI tool integrations. CloudBees Unify correlates this activity data with workflow execution to provide development cycle analysis that separates coding, review, and merge phases. This correlation reveals process bottlenecks that affect delivery performance measured in DORA and flow metrics.

Test insights correlate test execution data from CloudBees Unify workflow runs with test failure patterns and performance trends across components and environments. Security insights analyze security scanner results from workflow executions to track vulnerability trends and remediation effectiveness. Both contribute context to DORA metrics by revealing quality trends that affect deployment reliability and change failure rates within your specific CloudBees Unify configuration.

This integrated approach enables CloudBees Unify to surface correlations between operational constraints and delivery performance outcomes, transforming operational monitoring from reactive troubleshooting into proactive performance optimization guidance.

CloudBees Unify enables comprehensive performance analysis by correlating data across multiple analytics frameworks through its unified component and environment model, revealing relationships between operational patterns and business outcomes.

When DORA deployment frequency increases while flow metrics show decreased efficiency, CloudBees Unify surfaces this correlation through dashboard filtering that enables cross-analytics analysis within consistent time windows and component scopes. This correlation capability helps identify successful delivery automation coupled with value stream bottlenecks, guiding targeted improvement efforts.

CI insights provide explanatory context for DORA metric variations through CloudBees Unify’s integrated data correlation. High build queue wait times in CI insights correlate with increased deployment lead times in DORA metrics, while infrastructure failure patterns explain change failure rate spikes. The platform’s component-centric data model enables automatic correlation of operational constraints with delivery performance outcomes.

Security and test insights contribute improvement context by revealing how quality investments affect delivery velocity within your CloudBees Unify environment. Increased security scanning frequency might initially decrease deployment frequency but should improve change failure rates over time. CloudBees Unify enables tracking these trade-offs through coordinated analytics views that maintain consistent component and time scope filtering.

This correlation capability transforms CloudBees Unify analytics from measurement tools into improvement guidance systems. The platform reveals operational and process factors that drive performance variations, enabling evidence-based optimization decisions that account for the complex relationships between development practices, platform operations, and business outcomes.