> For the complete documentation index, see [llms.txt](https://docs.pagerly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pagerly.io/incidents-and-alerting/integrations/splunk.md).

# Splunk

Create Pagerly incidents automatically from Splunk alerts.

### Create the integration in Pagerly

1\. Navigate to <https://workspace.pagerly.io/inbound> and click **"Add Alert Integration"**.

2\. Set a display name, select the team this integration belongs to, choose the integration below, and click **"Add Integration"**.

3\. Copy the generated webhook URL - you will paste it into the tool in the next section.

### Configure Splunk

1\. Open the saved search you want to alert on and click **Save As → Alert**, or edit an existing alert.

2\. At the bottom of the alert configuration, click **Add actions +** and choose **Webhook**.

3\. Paste the Pagerly webhook URL into the **URL** field.

4\. Save the alert.

Splunk's webhook action sends a fixed payload, so there is nothing to paste:

```json
{
  "sid": "...",
  "search_name": "Checkout errors above threshold",
  "results_link": "https://splunk.example.com/...",
  "result": { "count": "128" },
  "owner": "admin",
  "app": "search"
}
```

### Notes

* **Deduplication** uses `search_name`, not `sid`. `sid` is unique to each firing, so keying on it would open a new incident every time the search ran. Using the search name groups repeated firings into one open incident.
* **Severity and status** are not present in Splunk's native payload, so both fall back to defaults. If your search emits them, point **Payload Mapping** at the relevant field.


---

# 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.pagerly.io/incidents-and-alerting/integrations/splunk.md?ask=<question>&goal=<user_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.