> 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/splunk.md).
# Splunk Integration
Send Splunk log or search‑based alerts to ilert, enabling on‑call engineers to react quickly to critical events uncovered in your data.
[The Splunk](https://www.splunk.com/) integration captures alerts from scheduled searches or log monitors and delivers them to on-call responders via ilert. By forwarding relevant technical alerts, your team can rapidly investigate critical events and reduce time to resolution based on log context.
## In ilert: Create a Splunk alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Splunk**, 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 Splunk: Create a search
1. Go to Splunk and then to **Search & Reporting.** Create a search for which you'd like to create an alert.
2. Click on **Save As** and then on **Alert** to add an alert
3. On the modal window name the alert e.g. **iLert,** choose **Webhook** in the **When triggered** section and **\*\*paste the** Webhook URL **that you generated in ilert and click on** Save\*\*
4. Finished! Your Splunk alerts will now create alerts in ilert.
## FAQ
**Will alerts in ilert be resolved automatically?**
No, unfortunately Splunk alerts do not fire resolve events.
**Can I connect Splunk with multiple alert sources from ilert?**
Yes, simply create more action sequences in Splunk.
---
# 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/splunk.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.
