Configure HTTP event collection

Configure the HTTP event collector (HEC) on a single-instance Splunk Enterprise deployment to ingest data using the Splunk Add-on for Amazon Kinesis Firehose.

Prerequisite

• Install the Splunk Add-on for Amazon Kinesis Firehose on a single-instance Splunk Enterprise deployment
• For optimal performance, set ackIdleCleanup to true in inputs.conf located in $SPLUNK_HOME/etc/apps/splunk_httpinput/local/inputs.conf for *nix users and %SPLUNK_HOME%\etc\apps\splunk_httpinput\local\inputs.conf for Windows users.

Steps

1. Decide what index you want to use to collect your Amazon Kinesis Firehose data. Ensure that this index is enabled and active. Sending data to a disabled or deleted index results in dropped events.
2. Go to Settings > Data inputs > HTTP Event Collector click Global Settings.
3. Check the box next to Enable SSL, then click Save.
4. Create an HTTP event collector token with indexer acknowledgments enabled. During the configuration:
5. Specify a Source type for your incoming data.
6. Select an Index to which Amazon Kinesis Firehose will send data.
7. Check the box next to Enable indexer acknowledgement.

Save the token that Splunk Web provides. You need this token when you configure Amazon Kinesis Firehose.

Repeat steps 4 and 5 for each additional source type from which you want to collect data. Each source type requires a unique HTTP event collector token.

Configure timestamp extraction

You can configure your add-on to send timestamped events to HTTP Event Collector when auto_extract_timestamp is set to "true" in the /event URL.

To configure this, enable one of the following endpoints:

• services/collector/event/1.0: Provides timestamps for event data events when auto_extract_timestamp is set to "true" in the /event URL
• services/collector/raw/1.0: Provides timestamps for raw data events when auto_extract_timestamp is set to "true" in the /event URL

When one or both of these endpoints are enabled, the add-on extracts timestamps as follows:

* If there is no timestamp in the event's JSON envelope, extraction is performed by leverage pipeline.
* If there is a timestamp, Splunk honors it.
* If "time=xxx" is used in the /event URL then auto_extract_timestamp is disabled.

https://docs.splunk.com/Documentation/Splunk/1/SimplerGDI/HECEndpoints#HEC_Endpoints