> For the complete documentation index, see [llms.txt](https://docs.lossless.io/aegis/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lossless.io/aegis/add-an-alert/alert-management.md).

# Alert management

Manage your alerts all in one place by navigating to Alerts on the navigation sidebar.

Here you will see all your alerts in a list across all your monitored addresses. The list will display your monitored address, the type of trigger, channel type, the name of your monitored address, chain, trigger counter, when it was created and quick access to edit or delete an alert.

You can adjust which columns you see in the list by clicking the Visibility and selecting the appropriate checkboxes.

Here are all the tools you can use on this view to find the right alert:

* Search by name or address.
* Filter by chain or trigger category.
* Sort by alert age and number of triggers.


---

# 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://docs.lossless.io/aegis/add-an-alert/alert-management.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.