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

# Splunk

Learn how to send events to Splunk from Couchdrop

## Overview

Couchdrop can send logging events directly to Splunk using the Splunk HTTP Event Collector (HEC).

This allows Couchdrop events to be forwarded into Splunk alongside logs from your other systems, where they can be searched, monitored, and incorporated into your existing logging workflows.

## How to connect to Splunk

{% hint style="warning" %}

#### Before you start

To connect Couchdrop to Splunk, you will need:

* A Splunk **Event Collector token**
* Your Splunk **HTTP Event Collector URI**
  {% endhint %}

{% stepper %}
{% step %}

### Open the Splunk logging connection

Log in to Couchdrop and navigate to **Admin Panel > Logging**.

Find the **Splunk** provider and select **Connect/Manage**.
{% endstep %}

{% step %}

### Select events to send to Splunk

Select the Couchdrop events that you want to send to Splunk.
{% endstep %}

{% step %}

### Configure Splunk

Enter your **Event Collector token** and **HTTP Event Collector URI**.

{% hint style="info" %}

#### Optional settings

The following configuration is optional:

* **Originating Host**
* **Event Source Application**
* **Sourcetype**
* **Index Name**

For information on configuring HTTP Event Collector access in Splunk, see the [Splunk HTTP Event Collector documentation](https://docs.splunk.com/Documentation/SplunkCloud/latest/Data/UsetheHTTPEventCollector).
{% endhint %}

{% endstep %}

{% step %}

### Save the Splunk connection

Click **Save Updates** to save the logging configuration.
{% endstep %}
{% endstepper %}


---

# 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.couchdrop.io/integrations/siem/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.