> 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/cortex-agentix/configure-cortex-agentix/cortex-agentix-data-sources-and-connectors/administration-and-troubleshooting/verify-collector-connectivity.md).

# Verify collector connectivity

Verify data collector connectivity and troubleshoot errors in Cortex AgentiX.

You can verify the connectivity status of a collector instance on the Data Sources & Integrations page. Instances are grouped by integration, and the **Instances Status** column shows icons that summarize the instance statuses for the integration. Click the integration to see details for each individual instance.

In addition, Cortex AgentiX creates Collection health issues if connectivity disruptions occur in your collection integrations, custom collectors, and Marketplace integrations. For more information, see [About health issues](/cortex-agentix/reference-and-developer-docs/troubleshoot/about-health-issues.md).

**Troubleshooting collector errors**

<details>

<summary>Where can I see if I have a connectivity error on a collector instance?</summary>

On the **Data Sources & Integrations** page, instances in error status display an error icon. Hover over the error icon next to the instance name to see the error message as received from the API.

</details>

<details>

<summary>Where can I trace the connectivity changes of a collector instance?</summary>

Each status change of an instance is logged in the `collection_auditing` dataset. Querying this dataset can help you see all the connectivity changes of an instance over time, the escalation or recovery of the connectivity status, and the error, warning, and informational messages related to status changes.

Example 8.

This example searches for status changes on Strata IOT integrations:

```programlisting
dataset = collection_auditing 
|filter collector_type = "STRATA_IOT"
```

</details>

<details>

<summary>How can I set up correlation rules to trigger collection issues?</summary>

Cortex AgentiX provides OOTB Collection issues that are triggered when a data collector instance is in error status, which means it is disconnected or not sending data. In addition, you can set up your own correlation rules that trigger collection issues for your specific needs. For example, you might want to be notified if a high-profile collector is in warning status so that you can fix the problem and prevent the collector from disconnecting.

Example 9. Example: Trigger collection issues for warning statuses on the STRATA\_IOT collector

In this example, a correlation rule triggers a Collection issue if an integration of the Strata IOT collector changes to warning status. Any issues will appear on the **Health Issues** page.

Example XQL:

```programlisting
dataset = collection_auditing 
|filter classification = "Warning" and collector_type = "STRATA_IOT"
```

Additional fields to specify in the correlation rule:

| Field             | Value                                                                                                                                                                                                                                                                                                                                              |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Time Schedule     | Hourly                                                                                                                                                                                                                                                                                                                                             |
| Query time frame  | 1 Hour                                                                                                                                                                                                                                                                                                                                             |
| Issue Suppression | Select **Enable issue suppression**.                                                                                                                                                                                                                                                                                                               |
| Action            | Select **Generate issue**.                                                                                                                                                                                                                                                                                                                         |
| Issue Domain      | Health                                                                                                                                                                                                                                                                                                                                             |
| Severity          | Medium                                                                                                                                                                                                                                                                                                                                             |
| Category          | <p>Collection</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>If an issue is triggered, the investigation options in the right-click menu of the <strong>Health Issues</strong> pages are context-specific. Make sure that you specify the relevant issue category.</p></div> |

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/cortex-agentix-data-sources-and-connectors/administration-and-troubleshooting/verify-collector-connectivity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.