> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/workbench-reference/search-for-an-event/find-an-event.md).

# Find an Event

You can search all events that were processed by [Ruxie](/workbench-reference/expel-terminology.md#ruxie) in the past 14 days, including those that were tuned or became Expel alerts.&#x20;

For example, you could use this feature to ensure Ruxie processed an EDR alert about a departing employee yesterday at 8:30am, or you could find events for a specific user that came from a specific IP address.

{% hint style="warning" %}
You can run a maximum of 100 searches in 24 hours.
{% endhint %}

## Search for Events <a href="#bridgehead-idm462186549670403360386458179" id="bridgehead-idm462186549670403360386458179"></a>

1. [Log in to Workbench](https://workbench.expel.io/auth/login?orig=%2F).
2. In the left side menu, select **Search for an Event**.
3. Click **Select parameter...**, then select a parameter for your search and enter a value for the parameter.

<div align="left"><figure><img src="https://2371323735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F82234aPbNfd179j5U4ti%2Fuploads%2FDlfO5jaoJnNrABsUldFE%2FScreenshot_2023-09-11_at_2_35_52_PM.png?alt=media&amp;token=11e30d69-52c1-4f2b-b3c8-e8ec11545354" alt="Image of the event search screen showing where to select parameters."><figcaption></figcaption></figure></div>

4. Select **Add another parameter** to enter an additional parameter, and then enter another value. You can repeat this process to add multiple search parameters.&#x20;

{% hint style="info" %}
Multiple parameters create a more targeted search. **However, be aware that the search uses the logical&#x20;*****'AND'*****&#x20;operator, so results must match all parameters.**
{% endhint %}

5. Select your specific device vendors (or leave it as "All Device Vendors"), and select the timeframe.
6. Select **Search**.
7. Workbench now searches for alerts in the evidence database, and then displays the 100 most recent results. You can view the event details by:
   * Selecting **Event Details** in the Time column.
   * Selecting the alert name in the Related Expel Alerts column (in cases where the event is linked to an [Expel Alert](/workbench-reference/alerts/how-expel-alerts-work.md)).

{% hint style="info" %}
Learn more in [About Event Details](/workbench-reference/search-for-an-event/about-event-details.md).
{% endhint %}

## Troubleshooting

If the search takes longer than 1 minute, it will time out. If this happens, try to make your search more specific and then run it again. You could do this by adding another parameter or by reducing the time period.


---

# 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://docs.expel.io/workbench-reference/search-for-an-event/find-an-event.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.
