This version of GitHub Enterprise Server was discontinued on 2024-09-25. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise Server. For help with the upgrade, contact GitHub Enterprise support.

About monitoring workflows

You can use the tools in GitHub Actions to monitor your workflows, metrics, and self-hosted runners.

In this article

Note: GitHub-hosted runners are not currently supported on GitHub Enterprise Server. You can see more information about planned future support on the GitHub public roadmap.

Monitoring your workflows

Using the visualization graph

Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows. For example:

Screenshot of the visualization graph of a workflow run.

For more information, see "Using the visualization graph."

Adding a workflow status badge

A status badge shows whether a workflow is currently failing or passing. A common place to add a status badge is in the README.md file of your repository, but you can add it to any web page you'd like. By default, badges display the status of your default branch. If there are no workflow runs on your default branch, it will display the status of the most recent run across all branches. You can display the status of a workflow run for a specific branch or event using the branch and event query parameters in the URL.

Screenshot of a workflow status badge. The left side contains the octocat logo and "GitHub Actions Demo", the name of the workflow. The right half is green with the text "passing."

For more information, see "Adding a workflow status badge."

Viewing workflow run history

You can view the status of each job and step in a workflow. For more information, see "Viewing workflow run history."

Monitoring self-hosted runners

If you use self-hosted runners, you can view their activity and diagnose common issues.

For more information, see "Monitoring and troubleshooting self-hosted runners."