> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/understand-your-business/ai-features/agents/agent-events.md).

# Agent Events

You can access agent events from two locations:

* [Agent Logs](/docs/understand-your-business/ai-features/agents/agents-create-and-configure.md)
* **Events** page

To view agent events on the Events page, select the **Agents** tab:

<img src="https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-39a08e8da7f4f9b738e9bad18087ebc1484f3a84%2Fd84f6eda67197a3d.png?alt=media" alt="" width="560">

From here, you can view and filter for agent events and build reports that you can then use to build widgets on the **Dashboard** page.

Each agent event card displays:

* Agent name.
* Timestamp marking the beginning of the flagged activity.
* Location where the agent detected the activity.
* An AI-generated description that explains why the agent flagged this activity/created an event.

<img src="https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-975ce08de064bed1a82f01dc58923e8f19490217%2F4975995454dcd1a4.png?alt=media" alt="" width="360">

You can filter the displayed agent events via the following agent-specific event filters:

* Agent Confidence Level
* Agent Description
* Agent Reason
* Agent State
* Agent Summary
* Agent Type


---

# 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://help.solink.com/docs/understand-your-business/ai-features/agents/agent-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.