> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/flow/list-of-forwarders/splunk-forwarding/apica-uf-proxy-app-extension/list-of-indexer-instances.md).

# List of Indexer Instances

You can launch the proxy to forward data to a one or more indexer instances directly by providing a list of Indexer URI's. This will put the indexers in a load balanced group for forwarding. The limitations here are that you need to know the list of indexers ahead of time. The proxy configuration wizard will ask you to provide the configuration parameters below

* Index to send data to
* Comma separated list of Splunk Indexer URI's - Host:Port e.g. idx1:9997,idx2:9997
* Workers - To scale up forwarding you can launch with multiple workers
* Version - The version of the forwarder to use. Apica can release new versions of the forwarder over time with newer capabilities.
  * Latest version of plugin is **logiqai/hauler-splstos:v1.5**


---

# 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.apica.io/flow/list-of-forwarders/splunk-forwarding/apica-uf-proxy-app-extension/list-of-indexer-instances.md?ask=<question>&goal=<endgoal>
```

`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.