Overview of event processing
Events are records of activity in log files, stored in Splunk indexes. They are primarily what Splunk Enterprise indexes. Events provide information about the systems that produce the log files. The term event data refers to the contents of a Splunk index.
Here's a sample event:
172.26.34.223 - - [01/Jul/2005:12:05:27 -0700] "GET /trade/app?action=logout HTTP/1.1" 200 2953
When Splunk indexes events, it:
- Configures character set encoding.
- Configures linebreaking for multi-line events.
- Identifies event timestamps (and applies timestamps to events if they do not exist).
- Extracts a set of useful standard fields such as
- Segments events.
- Dynamically assigns metadata to events, if specified.
- Anonymizes data, if specified.
For an overview of the Splunk Enterprise indexing process, see the Indexing overview chapter of the Managing Indexers and Clusters manual.
JMS/JMX - write your own
Configure character set encoding
This documentation applies to the following versions of Splunk® Enterprise: 5.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, 5.0.10, 5.0.11, 5.0.12, 5.0.13, 5.0.14, 5.0.15, 5.0.16, 5.0.17, 5.0.18