> 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/search-guard.md).
# Search Guard Integration
Connect Search Guard Signals alerts to ilert to forward watch-triggered events – like log‑based auth failures or node issues – to on‑call responders quickly.
By integrating [Search Guard](https://search-guard.com/) Signals with ilert, you can route custom-defined alerts – such as detected failed authentications, TLS certificate expirations, or node disconnects – from Elasticsearch logs or metrics into your on-call workflows. These technical alerts trigger ilert's escalation policies and ensure that responders are notified promptly, enhancing the security and operational stability of your cluster.
## In ilert: Create a Search Guard alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Search Guard**, 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**.
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 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 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.ilert.com/integrations/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 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.
