Splunk Cloud Platform

Getting Data In

Overview of event processing

The Splunk platform indexes events, which are records of activity that reside in machine data. Events provide information about the systems that produce the machine data. The term event data refers to the contents of a Splunk platform index.

Here is a sample event:

172.26.34.223 - - [01/Jul/2017:12:05:27 -0700] "GET /trade/app?action=logout HTTP/1.1" 200 2953

When Splunk software indexes events, it does the following tasks:

Task Link
Configures character set encoding Configure character set encoding
Configures line breaking for multi-line events Configure event line breaking
Identifies event timestamps and applies timestamps to events if they don't exist Configure event timestamps
Extracts a set of useful standard fields, such as host, source, and sourcetype About default fields
Segments events About event segmentation
Dynamically assigns metadata to events, if specified Assign default fields dynamically
Anonymizes data, if specified Anonymize data

For an overview of the indexing process, see the Indexing overview chapter of the Managing Indexers and Clusters of Indexers manual.

Last modified on 31 March, 2021
Overview of the Splunk OpenTelemetry Collector for Kubernetes   Configure character set encoding

This documentation applies to the following versions of Splunk Cloud Platform: 8.2.2112, 8.2.2201, 8.2.2202, 8.2.2203, 9.0.2205, 9.0.2208, 9.0.2209, 9.0.2303, 9.0.2305, 9.1.2308, 9.1.2312, 9.2.2403, 9.2.2406 (latest FedRAMP release), 9.3.2408


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters