> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/monitor-data-source-instances-health.md).

# Monitor data source instances health

You can monitor the health and status of your integrated data source instances and their repositories. Tracking and analyzing this data allows you to understand and troubleshoot errors, mitigate detected vulnerabilities, and ensure the reliability of your data sources.

#### How to view an instance health

1. Navigate to Settings → **Data Sources & Integrations**.
2. Filter for a data source such as GitHub (SaaS).

   The data source is displayed, including the number of connected instances and their statuses. Status options include Connected, Error, Warning, and Disabled.
3. Select the relevant data source.

   A list of data source instances is displayed.
4. Select an instance.
5. Click the **Review health** link.

   The health status page opens, displaying:

   * The status of the instance, connected repositories and instance type, such as cloud are displayed on the top card
   * A list of repositories connected to the instance, including scan details such as status, scan coverage (connected scanners such as SCA, Secrets and IaC and the scan status), location (scanned branch, organization, repository) and timestamp

**Understanding errors and warnings**

* An error status is displayed if:
  * More than 50% of the repositories associated with the instance have errors
  * There is a token error for a repository
  * There are missing permissions (categorized as an error based on severity)
  * Webhook subscription errors (categorized as an error based on severity)
  * At least one repository includes a warning
* A warning status is displayed if:
  * Less than 50% of the repositories associated with the instance have errors
  * Missing permissions (categorized as a warning based on severity)
  * Webhook subscription errors (categorized as a warning based on severity)

**Troubleshoot health**

You can troubleshoot both instance and repository issues.

1. Select an instance containing an error or warning status.
2. **Review instance issues**: click Review Health in the top bar.

   A list of errors by repository and related to the instance are displayed. The list includes these unique properties:

   * **Classification**: Options: **Warning** or **Error**
   * **Error Type**: The type of instance error. Options: Permission, Clone, Connection, Webhook subscription, Token
   * **Repository**: the repository containing the issue
   * **Scope**: the scope of the issue
3. **Review repository issues**: select a repository in the table with a status of **Error** or **Warning**.

   A list of repository-related warnings and errors is displayed, including details such as description, type, location, and timestamp.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/application-security/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/monitor-data-source-instances-health.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.