> 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-xdr-3.x/cortex-xdr-3.x-documentation/data-management/data-ingestion/verifying-collector-connectivity.md).

# Verifying collector connectivity

{% hint style="info" %}

### Notice

Ingestion of logs and data requires a Cortex XDR Pro per GB license.
{% endhint %}

You can verify the connectivity status of a collector instance on the Collection Integrations page. Instances are grouped by integration, and a status icon shows a summary of instance statuses for each integration. Expand the integration section to see the status of each individual instance, and hover over the status icons to see details about warning or error statuses.

**Troubleshooting collector errors**

{% hint style="info" %}

### Note

For more information on troubleshooting data collector applet errors, see [Troubleshoot Broker VM applet errors](/cortex-xdr-3.x/cortex-xdr-3.x-documentation/data-management/broker-vm/troubleshoot-broker-vm-applet-errors.md).
{% endhint %}

<details>

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

On the Collection 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:&#x20;

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 alerts?</summary>

You can create correlation rules that are based on the fields in the `collection_auditing` dataset.

Example: Trigger collection alerts for error statuses on the STRATA\_IOT collector

In this example, a correlation rule triggers an alert if an integration of the Strata IOT collector changes to error status.

Example XQL:

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

Additional fields to specify in the correlation rule:

| Field             | Value                                |
| ----------------- | ------------------------------------ |
| Time Schedule     | Hourly                               |
| Query time frame  | 1 Hour                               |
| Alert Suppression | Select **Enable alert suppression**. |
| Action            | Select **Generate alert**.           |
| Severity          | Medium                               |
| Category          | Collection                           |

</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 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/cortex-xdr-3.x/cortex-xdr-3.x-documentation/data-management/data-ingestion/verifying-collector-connectivity.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.