Question

Your team runs a critical GitHub Actions CI/CD workflow across dozens of repositories. Leadership asks you to track pipeline health metrics such as workflow run duration trends, failure rates, and which jobs are the slowest bottlenecks over the last 90 days — without exporting data to an external system. Which built-in GitHub capability should you use to satisfy this request?

Accepted Answer

Enable the repository's Actions usage metrics and workflow run history under the Insights tab to visualize run duration, success/failure rates, and job-level timing

Answer

Add a step to each job that writes timing data to the GITHUB_STEP_SUMMARY file so metrics appear in the run summary

Answer

Configure a scheduled workflow that queries the REST API for run results and posts them to a repository issue for tracking

Answer

Turn on debug logging with ACTIONS_STEP_DEBUG to capture detailed timing information for each job