https://docs.splunk.com/Documentation/Splunk/8.0.5/Deploy/Datapipeline
"In the input segment, Splunk software consumes data. It acquires the raw data stream from its source, breaks in into 64K blocks, and annotates each block with some metadata keys." Reference: https://docs.splunk.com/Documentation/Splunk/8.0.5/Deploy/Datapipeline

https://docs.splunk.com/Documentation/Splunk/8.2.2/Data/Howdoyouwanttoadddata The fastest way to add data to your Splunk Cloud instance or Splunk Enterprise deployment is to use Splunk Web. After you access the Add Data page, choose one of three options for getting data into your Splunk platform deployment with Splunk Web: (1) Upload, (2) Monitor, (3) Forward The Upload option lets you upload a file or archive of files for indexing. When you choose Upload option, Splunk Web opens the upload process page. Monitor. For Splunk Enterprise installations, the Monitor option lets you monitor one or more files, directories, network streams, scripts, Event Logs (on Windows hosts only), performance metrics, or any other type of machine data that the Splunk Enterprise instance has access to.

Splunk REST API is a valid method to create a Splunk user. The Splunk REST API allows administrators to create, edit, and delete users programmatically using HTTP requests. The other options are not valid methods to create a Splunk user. Creating a support ticket does not create a user, but requests assistance from Splunk support. Creating a user on the host operating system does not create a Splunk user, but a system user. Adding the username to users.conf does not create a user, but modifies the configuration file that stores user information. References = Configure users with the CLI, Configure users and roles