Getting Data In

How to configure Splunk to parse multiple logs as individual events, not a single event?

cj039165
New Member

Hello –

New to Splunk. I’ve searched the community, but may not be using the correct wording to find an answer. See the example below of a log file I’m feeding into Splunk. Each event starts at the time stamp and ends after the “blah, blah”. When I search the log in Splunk, it’s showing multiple events together. How do I go about getting Splunk to see them as individual events?

09:16:54,126 DEBUG  [Thread-1646678] Version: 0.2
Message Format: X12
Message Type: 271_Response_005010X279A1
Status: 
Body Length: 2128

ISA blah blah blah ect

09:18:57,357 DEBUG  [Thread-1646478] Version: 0.2
Message Format: X12
Message Type: 271_Response_005010X279A1
Status: 
Body Length: 2128

ISA blah blah blah ect
0 Karma

pradeepkumarg
Influencer

Splunk distinguishes each event based on the LINE_BREAKER property set for that sourcetype in props.conf. props.conf should be on your indexer(s)

http://docs.splunk.com/Documentation/Splunk/6.4.1/Admin/Propsconf

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...