Create an HTTP event collector token for Splunk App for AR and Edge Hub

To send data to your Splunk platform instance using the HTTP event collector (HEC), Splunk App for AR and Edge Hub requires a HEC token.

Prerequisite

Complete the requirements at Get started with Splunk Edge Hub OS in the Splunk Edge Hub OS Setup and Configuration Guide.

Steps

Create the HEC token where you've configured the HEC to collect data from your Splunk Edge Hub device.

When configuring the HEC token, configure the following fields:

• Name the token anything you'd like. For example, splunk_edge_hub_default
• Ensure that indexes created for Splunk Edge Hub OS are allowed for this token. See the previous step, Create indexes for Splunk Edge Hub OS to review the indexes you created.
• For the default index dropdown, select edge_hub_data.

No other fields require configuration.

Splunk Cloud Platform

If you're using Splunk Cloud Platform, see Manage HTTP Event Collector (HEC) tokens in Splunk Cloud Platform in the Splunk Cloud Platform Admin Config Service Manual manual.

Splunk Enterprise

If you're using Splunk Enterprise, see Create an Event Collector token on Splunk Enterprise in the Splunk Enterprise Getting Data In manual.

In a single-instance deployment, create the HEC token on the single instance. In a distributed deployment, create the HEC token on the heavy forwarder.

Next step

Configure user permissions for your Splunk Edge Hub deployment. Specific permissions are required to complete the device registration process. See Configure permissions for Splunk App for AR and Edge Hub.

For an overview of installation and configuration steps, see Installation and configuration overview for Splunk Edge Hub OS in the Splunk Edge Hub OS Setup and Configuration Guide.