> 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/~/changes/vPSzQFfkdJCVWGT5AL1m/inbound-integrations/search-guard.md).
# Search Guard Integration
With the ilert Search Guard integration, you can create alerts in ilert based on Search Guard alerts.
## In ilert: Create a Search Guard alert source
1. Go to **Alert sources** --> **Alert sources** and click on **Create new alert source**
2. Search for **Search Guard** in the search field, click on the Search Guard tile and click on **Next**.
3. Give your alert source a name, optionally assign teams and click **Next**.
4. Select an **escalation policy** by creating a new one or assigning an existing one.
5. Select you [Alert grouping](/~/changes/vPSzQFfkdJCVWGT5AL1m/alerting/alert-sources.md#alert-grouping) preference and click **Continue setup**. You may click **Do not group alerts** for now and change it later.
6. The next page show additional settings such as customer alert templates or notification prioritiy. Click on **Finish setup** for now.
7. On the final page, an API key and / or webhook URL will be generated that you will need later in this guide.
## In Search Guard: Create watch
1. Go to Search Guard to open the main menu and choose **Search Guard -> Signals**
2. On the next page click on the **New** button to create a new watch
3. On the next view name the watch e.g. **My Watch** scroll down and configure the watch to your liking.
4. Scroll down to **Actions** and add the **Webhook** action
5. Name the action e.g. **iLert**, paste the **Webhook URL** that you generated in ilert, change headers as required and paste the following **json** as body template
```
{
"incidentKey": "{{watch.id}}",
"summary": "SearchGuard alert: {{watch.id}}",
"details": "Problem occurred at {{execution_time}}",
"serverUrl": "https://my-server.com"
}
```
6. Click on **Create** to save the watch.
7. Finished! Your Elastic Search Guard alerts will now create alerts in ilert.
## FAQ
**Will alerts in ilert be resolved automatically?**
No, unfortunately Search Guard watch(es) will not fire resolve events for alerts.
**Can I connect Search Guard with multiple alert sources from ilert?**
Yes, simply create more watches in Search Guard.
---
# 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/~/changes/vPSzQFfkdJCVWGT5AL1m/inbound-integrations/search-guard.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.
