# Splunk Forwarding

After ingestion, data can be forwarded to a Splunk instance. Apica Ascent supports two primary approaches for forwarding data to Splunk:

1. **Using Splunk Forwarders**
   1. HEC Forwarder
   2. Syslog Forwarder (uses TCP)
   3. Syslog CEF Forwarder (uses TCP)
2. **Using a Splunk Forwarder Proxy Source Extension**

The **Forwarder Proxy Source Extension** is recommended when advanced delivery guarantees are required, such as queueing, retries, acknowledgments, backpressure handling, and load balancing. It can also be chosen when data needs to be forwarded to multiple indexers.

The **Ascent Splunk Forwarders** (HEC, Syslog, Syslog CEF) are suitable for lighter workloads where indexer load is not significant and successful delivery is generally assured.


---

# Agent Instructions: 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:

```
GET https://docs.apica.io/flow/list-of-forwarders/splunk-forwarding.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.