> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/inbound-integrations/thousandeyes.md). # Cisco ThousandEyes Integration Connect ilert and ThousandEyes and receive critical notifications via SMS, push, voice and messenger notifications [ThousandEyes by Cisco](https://www.thousandeyes.com/) is a network intelligence platform that monitors the performance of internet-based networks and applications, helping businesses quickly detect and troubleshoot connectivity issues. By connecting it to ilert, users can receive real-time alerts on network disruptions, ensuring rapid response and minimal downtime for critical services. ## In ilert: Create a Cisco ThousandEyes alert source 1. Go to **Alerting** → **Alert sources** and click **Create new alert source**. 2. Search for **Cisco ThousandEyes**, click its tile, and click **Next**. 3. Give your alert source a name, optionally assign teams, and click **Next**. 4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.
The escalation step of the ilert alert source wizard, headed Who should be notified about alerts, with an escalation policy selected and a preview of its escalation rules below.

Pick an existing escalation policy, or generate a basic one without leaving the wizard.

5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving. 6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later. 7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.
## In Cisco ThousandEyes: Create a Webhook 1. On the sidebar, click on **Integrations**.
2. Now click on the **New Integration** button.
3. Select **Custom Webhook**.
4. Enter a **Name** and the previously generated alert source **URL** into corresponding input fields. 5. Choose **Generic** in the **Preset Configurations** selection and click on **Test**.
6. To verify if the webhook is working, check the **Status**; it should show **Connected**.
7. Now open the three-dot menu and click on **Manage Alert Rules**.
8. Select the desired **Alert Rules** from which you want to receive notifications. 9. Click on **Save** to finish the setup.
## FAQ **Will alerts in ilert be resolved automatically?** Yes, as soon as Cisco ThousandEyes sends a notification with '1' status, corresponding alerts in ilert will be resolved automatically. --- # 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.ilert.com/integrations/inbound-integrations/thousandeyes.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.