> 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/investigate-and-respond-to-incidents/investigate-alerts/triage-and-investigate-alerts/investigate-contributing-events.md).

# Investigate contributing events

You can investigate the events created by an alert.

{% hint style="info" %}

### Notice

This functionality requires a Cortex XDR Pro license.
{% endhint %}

When investigating an alert generated by a correlation rule, you can view all of the events created for the alert. You can have up to 1000 events per correlation rule.

In addition, if the correlation rule includes a drilldown query you can run the query in the **Query Builder**. The drilldown query provides additional information about an alert for further investigation.

How to investigate contributing events

1. From the **Alerts** page, locate an alert created by a correlation rule.
2. Right-click the row, and select Manage Alert → **Investigate Contributing Events**.
3. (Optional) Open the drilldown query, if available.

   Right-click the row and select Manage Alert → **Open Drilldown Query**.

   The drilldown query can accept parameters from the alert output for the correlation rule. In addition, the alert time frame used to run the drilldown query provides more details about the alert generated by the correlation rule. The alert time frame is the minimum and maximum timestamps of the events for the alert. If there is only one event, the event timestamp is the time frame used for the query.


---

# 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-xdr-3.x/cortex-xdr-3.x-documentation/investigate-and-respond-to-incidents/investigate-alerts/triage-and-investigate-alerts/investigate-contributing-events.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.