> 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/splunk-http-event-collector-hec-forwarder/non-metric-indexes.md).

# Non Metric Indexes

Apica supports forwarding to splunk log indexes. 

Use this option to forward **logs or structured events** into standard Splunk **log/event indexes**.

Creating a splunk hec forwarder for logs is straight forward and uses the *"\_json"* type when creating the forwarder

### Configuration Example:

| Field        | Value                        |
| ------------ | ---------------------------- |
| **Host**     | `https://splunk.company.com` |
| **Port**     | `8088`                       |
| **User**     | `admin`                      |
| **Password** | `<your-hec-token>`           |
| **Type**     | `_json`                      |

> Ensure the Splunk index receiving these events is a **standard event/log index**, not a metric index.

<figure><img src="/files/oHGSWxwDXkEEJQUi6M7h" alt=""><figcaption><p>Configuration example for a Non Metric Index Forwarder</p></figcaption></figure>


---

# 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/splunk-http-event-collector-hec-forwarder/non-metric-indexes.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.