Actionable CI Insights

The Insights section gives you a quick overview of key CI pipeline metrics and highlights any changes that might affect performance. It’s set up to help DevOps teams spot and fix bottlenecks fast, keeping the CI process running smoothly and efficiently.

Insights Table on the Dashboard

The Insights section provides a quick look into important CI pipeline metrics and surfaces any changes that are most likely impacting performance. This setup allows DevOps teams to quickly identify potential bottlenecks and take action to maintain the CI process’s efficiency and continuity.

Each row in the table below shows one metric or rule being monitored, including information on recent changes:

• Rule: Details the specific metric or issue.
• Count: Indicates how many workflows are affected by this issue.
• Priority: Color-coded tags, such as High or Low, to prioritize focus areas.

This table offers an at-a-glance view of which aspects of your CI performance need attention, allowing you to address the most critical issues first. Gray-colored insights indicate no current issues in that category, meaning the metric is within safe boundaries.

What Are the Insight Rules?

Decreasing Success Rate

Tracks declines in workflow success rate, indicating successful runs over time.

A drop in success rate means more workflows are failing, causing delays, more troubleshooting, and reduced CI pipeline stability. This metric simplifies spotting and resolving issues, like flaky tests or misconfigurations.

Increasing Duration

Monitors workflows taking longer to complete, showing an increase in average duration.

Longer pipelines delay the entire development process by delivering feedback later. This rule helps in identifying inefficiencies, such as slow test runs, lengthy builds, or limited resources that might need attention.

Test Failures

Highlights workflows with repeated test failures.

Frequent test failures often signal issues with code quality or test design. Monitoring this helps detect and fix unreliable tests, reduce false alarms, and uphold code quality. Reliable tests are essential for CI trust and minimizing unnecessary debugging.

Increasing MTTR (Mean Time to Recovery)

Tracks recovery time after CI pipeline failures

Longer MTTRs indicate a slower recovery process, increasing downtime. This rule helps maintain a responsive CI process, promoting faster recovery times and minimal disruption, which boosts team productivity.

Decreasing Run Counts

Monitors the frequency of workflow runs.

Lower run counts may reflect reduced CI activity due to fewer commits, missed schedules, or altered CI triggers. Tracking this helps identify CI setup issues, ensuring the CI system runs consistently and detects issues early.

Detailed View of Each Insight

Clicking any item in the Insights table opens a detailed view for that metric or rule, showing:

Metrics Graph and Insight Information:

A historical graph with Elite and Median thresholds for visualizing performance trends over time.

Each chart in CICube is compared against two benchmarks to help you see how your pipeline is doing:

• Elite Threshold: This shows the performance level that top industry teams are hitting.
• Median Threshold: This represents the average performance across the industry.

These benchmarks provide a quick way to see how your pipelines compare to industry standards, making it easier to identify areas for improvement.

For instance, if one of your workflows’ success rates falls below the Elite threshold, you’ll see a graph showing its decline, a list of recent failures, and tips to help you get it back on track.

Run Information

It displays recent runs that contributed to the metric change, enabling you to trace issues back to specific commits, branches, or contributors.

AI-Driven Suggestions for Improvement

It also provides actionable recommendations powered by AI, aimed at enhancing the metric's performance to stay within Elite thresholds.

The Optimization & Suggestions section offers AI-driven recommendations to improve your workflows. This is particularly useful if any of your pipelines fall below Elite thresholds, listing workflows with potential performance issues and suggesting specific actions to get them running more smoothly.