[EDI] About the tool status page for code scanning (#59706)

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com>

Author: 3 people

content/code-security/concepts/code-scanning/index.md

@@ -20,4 +20,5 @@ children:
   - /sarif-files
   - /merge-protection
   - /codeql
+  - /tool-status-page
 ---

content/code-security/concepts/code-scanning/tool-status-page.md

@@ -0,0 +1,93 @@
+---
+title: About the tool status page
+shortTitle: Tool status page
+intro: 'The {% data variables.code-scanning.tool_status_page %} provides visibility into the health and performance of {% data variables.product.prodname_code_scanning %} tools in your repository.'
+permissions: '{% data reusables.permissions.code-scanning-all-alerts %}'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Code Security
+  - Code scanning
+  - CodeQL
+contentType: concepts
+---
+
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+## What is the {% data variables.code-scanning.tool_status_page %}?
+
+The {% data variables.code-scanning.tool_status_page %} shows information about all of your {% data variables.product.prodname_code_scanning %} tools and is a good starting point for debugging problems when {% data variables.product.prodname_code_scanning %} isn't working as expected.
+
+> [!NOTE]
+> The {% data variables.code-scanning.tool_status_page %} shows tool status at the repository level for the default branch only, not at the organization level.
+
+## Tool status indicators
+
+The {% data variables.code-scanning.tool_status_page %} displays one of three statuses:
+
+* **All configurations are working**: All tools are operating as expected
+* **Some configurations need attention**: Some tools have warnings or non-critical issues
+* **Some configurations are not working**: One or more tools have critical errors
+
+## What information is available
+
+### For all {% data variables.product.prodname_code_scanning %} tools
+
+* Configuration status and health
+* Scan scheduling
+* First and most recent scan times
+* Rules used in scans
+
+### For integrated tools like {% data variables.product.prodname_codeql %}
+
+In addition to the information listed above, the {% data variables.code-scanning.tool_status_page %} for integrated tools provides the following details:
+
+* File coverage percentages by programming language
+* Configuration details for each setup type
+* Specific error messages
+* Downloadable CSV reports of analyzed files
+* Downloadable lists of rules used and alert counts
+
+## How {% data variables.product.prodname_codeql %} defines scanned files
+
+{% data variables.product.prodname_codeql %} reports a file as scanned if some lines of code in that file were processed.
+
+### Interpreted languages
+
+* **Default setup**: Scanned files include all source code files for languages {% data variables.product.prodname_codeql %} can analyze
+* **Advanced setup**: You can use `paths` and `paths-ignore` to define which files to scan. See [AUTOTITLE](/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning-with-codeql).
+
+### Compiled languages
+
+The {% data variables.code-scanning.tool_status_page %} reports files present before running autobuild or manual build steps. Files generated during the build process are not shown. See [AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages#about-autobuild-for-codeql).
+
+### Coverage calculation
+
+File coverage percentages respect any files excluded by `paths` and `paths-ignore` configuration properties.
+
+## Understanding file coverage percentages
+
+Use file coverage percentages to debug and improve your analysis:
+
+* **High percentage**: {% data variables.product.prodname_code_scanning_caps %} is working as expected for that language
+* **Low percentage**: Investigate diagnostic output. See [AUTOTITLE](/code-security/code-scanning/troubleshooting-code-scanning/codeql-scanned-fewer-lines-than-expected)
+* **Zero percentage**: You may have code in languages not currently being analyzed. Update your setup to include these languages. See [AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning#changing-the-languages-that-are-analyzed)
+
+> [!NOTE]
+> If you set up both advanced setup and default setup, the {% data variables.code-scanning.tool_status_page %} only shows default setup.
+
+## Troubleshooting features
+
+The {% data variables.code-scanning.tool_status_page %} helps you troubleshoot issues through:
+
+* **Error messages**: Explains why tools aren't performing as expected with suggested actions
+* **File coverage data**: Shows which files and languages are being analyzed
+* **Configuration details**: Displays information about each analysis run
+* **Downloadable reports**: Provides CSV reports with detailed file and rule information
+
+## Further reading
+
+* [AUTOTITLE](/code-security/how-tos/scan-code-for-vulnerabilities/manage-your-configuration/use-the-tools-status-page-for-code-scanning)

content/code-security/how-tos/scan-code-for-vulnerabilities/manage-your-configuration/about-the-tool-status-page.md

@@ -19,8 +19,8 @@ topics:
 redirect_from:
   - /code-security/code-scanning/managing-your-code-scanning-configuration
 children:
-  - /about-the-tool-status-page
   - /editing-your-configuration-of-default-setup
+  - /use-the-tools-status-page-for-code-scanning
   - /set-code-scanning-merge-protection
   - /configuring-larger-runners-for-default-setup
   - /codeql-code-scanning-for-compiled-languages