> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/infinity/monitoring-and-alerts/about-infinity-alerts.md).
# About Infinity alerts
Alerts display the SIMs where the usage has exceeded alert thresholds. These are generated by the alerting system and used to initiate orchestrations.
You can [view alerts](#viewing-alerts) and [filter alerts](#filtering-the-displayed-alerts).
{% hint style="info" %}
Alerts can trigger notifications. You must subscribe to receive them. For more information, see [Managing your Infinity user profile](/infinity/account-and-support/how-to-manage-your-infinity-user-profile.md).
{% endhint %}
To access the Infinity alerts:
1. On the left menu, select **Connect & Manage**.
1. Select **Alerts** to view the alerts list.
## Viewing alerts
The **Alerts** list contains the following fields:
| Field | Description |
| ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Date | The date and time of the change, formatted as `dd/mm/yyyy hh:mm:ss`. |
| Type | Displays Finance, Data, Messaging, IMEI, or Calls alerts. For more information, see [Creating alert profiles](/infinity/monitoring-and-alerts/about-infinity-alert-profiles.md). |
| ICCID | Displays the alerts triggered for a specific ICCID. |
| Subject | A short summary about the change made to the alert record, for auditing purposes. |
To view Infinity alerts:
1. On the **Alerts** page, select **View**.
### Filtering the displayed alerts
Use the available search filters to refine the **Alerts** list:
| Search filter | Description | Example |
| ------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Start Date | Displays alerts triggered on or after the chosen date. | `21/03/2024` returns alerts generated on or after March 21, 2024. |
| End Date | Displays alerts triggered up to and including the chosen date. | `21/03/2024` returns alerts generated on or before March 21, 2024. |
| Type | Displays alerts where Finance, Data, Messaging, IMEI, or Calls thresholds are breached. | `IMEI` returns alerts triggered because the SIM moved to another device. |
| ICCID | Displays alerts triggered for a specific ICCID. | `89445385230249074` returns alerts associated with that ICCID. |
To filter alerts:
1. On the **Alerts** page, select the **View** tab.
2. Select **Start Date** to filter alerts from a date.
3. Select **End Date** to filter alerts up to a date.
4. Select **Type** to filter alerts by threshold.
5. Select **ICCID** to filter results by SIM.
6. Select **Filter** to return matching results.
7. Select **Reset** to clear all applied filters.
---
# 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.eseye.com/infinity/monitoring-and-alerts/about-infinity-alerts.md?ask=&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.
