Set up and use HTTP Event Collector from the CLI

You can use the http-event-collector parameter of the Splunk command line interface (CLI) and its options to administer an HTTP Event Collector (HEC) instance on a Splunk Enterprise server.

It's not possible to use HEC on a Splunk Cloud instance from the CLI. If you have a Splunk Cloud instance, log into the instance and manage HEC from Splunk Web instead.

For more information about the CLI, see the following topics in the Splunk Enterprise Admin Manual:

• About the CLI
• Use the CLI to administer a remote Splunk server

CLI syntax

There are two syntaxes to use when you administer HEC through the CLI:

• The syntax for all other HEC actions, such as creating, deleting, and showing tokens
• The syntax for sending data to HEC

Use the following syntax for all actions except sending data to HEC:

splunk http-event-collector <command> <token-name> [<option2>] [<-parameter1> <value1>] [<-parameter2> <value2>] <data>

All HTTP Event Collector commands except for send assume that the first option following the command name is the name of the token. In addition, the create command assumes that the second option is a description of the token in quotation marks.

Use the following syntax to send data to the HEC:

splunk http-event-collector send -uri <uri_value> -name <token-name> <data>

If you want to apply the CLI commands to the global configuration, don't include the -name <token-name> argument. For example, the following syntax enables HTTP Event Collector:

splunk http-event-collector enable -uri <uri_value> <data>

Supported CLI commands

The following HTTP Event Collector-specific CLI commands are supported in Splunk Enterprise:

Command	Description
create	Create a new token.
delete	Remove a token.
list	Show all available tokens.
update	Change token properties.
enable	Enable a token.
disable	Disable a token.
help	Show help.
send	Send data to an endpoint.

Supported CLI parameters

HEC supports the following CLI parameters. You must immediately follow a CLI parameter with its value. Enclose any values that contain spaces in quotation marks.

Parameter	Description
-uri	The Uniform Resource Identifier (URI) of the Splunk server that takes the form scheme://host:port. As an alternative to setting this parameter, you can set the $SPLUNK_URI environment variable instead. The port number to use must be the management port of your Splunk server (8089by default), and not the HTTP Event Collector port (8088by default).
-auth	Splunk server user authentication in the form username:password. If this parameter is missing, you are prompted for a username and password.
-name	The name of the token.
-disabled	Whether to disable the token. 1 indicates true and 0 indicates false.
-description	A description of the token.
-indexes	A list of indexes accepted by the token.
-index	The token default index. Splunk Enterprise assigns this value to data that doesn't already have an index value set.
-source	The token default source value. Splunk Enterprise assigns this value to data that doesn't already have a source value set.
-sourcetype	The token default sourcetype value. Splunk Enterprise assigns this value to data that doesn't already have a sourcetype value set.
-outputgroup	The token default output group value. An output group is a group of indexers set up by the Splunk software administrator to index the data. Splunk Enterprise assigns this value to data that doesn't already have an output group value set.
-port	The HTTP Event Collector server port. The default value is 8088, but you can change it using this parameter.
-enable-ssl	Whether the HTTP Event Collector server protocol is HTTP or HTTPS. 1 indicates HTTPS and 0 indicates HTTP.
-dedicated-io-threads	The number of dispatcher threads on the HTTP Event Collector server. The default value is 2. Do not alter this setting unless you have been requested to do so by Splunk Support. The value of this parameter can't be more than the number of physical CPU cores on your Splunk Enterprise server.
-output-format	The output format. txt indicates text and json indicates JSON. The default value is txt.

Example CLI syntax

The following example CLI entry creates a token called new-token, assigns it the given URI, gives it a description, sets it to disabled, and indicates that the HTTP Event Collector data is to be saved to the log index.

splunk http-event-collector create new-token -uri https://localhost:8089 -description "this is a new token" -disabled 1 -index log

The following example CLI entry enables a token called myapp, assigns it the given URI, and sets the user authentication:

splunk http-event-collector enable -name myapp -uri https://localhost:8089 -auth admin:changeme

The following example CLI entry sends data to HTTP Event Collector using the given token and URI.

splunk http-event-collector send -uri https://localhost:8089 -token new-token {"this is the data to send"}