English
No results found.

Explore by product

GitHub Actions
  • Get started
  • Account and profile
  • Authentication
  • Repositories
  • GitHub
  • Enterprise administrators
  • Billing and payments
  • Organizations
  • Code security
  • GitHub Issues
  • GitHub Actions
  • GitHub Codespaces
  • GitHub Packages
  • Search on GitHub
  • Developers
  • REST API
  • GraphQL API
  • GitHub CLI
  • GitHub Discussions
  • GitHub Sponsors
  • Building communities
  • GitHub Pages
  • Education
  • GitHub Desktop
  • Atom
  • Electron
  • CodeQL
  • npm
    • English
  • English
  • 简体中文 (Simplified Chinese)
  • 日本語 (Japanese)
  • Español (Spanish)
  • Português do Brasil (Portuguese)

    • This version of GitHub Enterprise was discontinued on 2021-09-23. 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. For help with the upgrade, contact GitHub Enterprise support.

    Article version

    In this article

    About monitoring and troubleshooting

    You can use the tools in GitHub Actions to monitor and debug your workflows.

    Note: GitHub Actions was available for GitHub Enterprise Server 2.22 as a limited beta. The beta has ended. GitHub Actions is now generally available in GitHub Enterprise Server 3.0 or later. For more information, see the GitHub Enterprise Server 3.0 release notes.


    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

    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. You can also display the status of a workflow run for a specific branch or event using the branch and event query parameters in the URL.

    example status badge

    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 example:

    Name of workflow run

    For more information, see "Viewing workflow run history."

    Troubleshooting your workflows

    Using workflow run logs

    Each workflow run generates activity logs that you can view, search, and download. For example:

    Super linter workflow results

    For more information, see "Using workflow run logs."

    Enabling debug logging

    If the workflow logs do not provide enough detail to diagnose why a workflow, job, or step is not working as expected, you can enable additional debug logging. For more information, see "Enabling debug logging."

    Monitoring and troubleshooting 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."