Getting Data In

how to remove multiple logs into single event

duggp007
New Member

[tomcat]
EXTRACT = \/u01\/logs-(?\w+)\/.* in source

Adding the below to BREAK EVENTS only at timestamp and TRUNCATING issue

BREAK_ONLY_BEFORE = (\d+[- :,-w]+)
MAX_TIMESTAMP_LOOKAHEAD = 30
TRUNCATE = 0

We are facing an issue with multiple logs in a single event for only tomcat as the sourcetype,

May I know the reason for it.
we also have
SHOULD_LINEMERGE=true for other sourcetype should I include SHOULD_LINEMERGE=false for the tomcat.

Any help will be appreciated.

0 Karma

woodcock
Esteemed Legend

You should always avoid the BREAK_* settings and use only SHOULD_LINEMERGE=false and LINE_BREAKER = Your RegEx Here.

0 Karma

gcusello
SplunkTrust
SplunkTrust

HI duggp007,
surely you have to review your parsing.
To do this I suggest to take an extract of your logs with all the kind of logs in the same sourcetype (e.g. tomcat) in a text file.
Then ingest it for test using the guided procedure in web interface [Settings -- Add Data] so you can find the correct options yo use for thst sourcetype.
Probably is uncorrect the TIME_PREFIX and/or the TIME_FORMAT, so, sometimes, Splunk cannot recognize the start of an event and doesn't correctly break it.

Bye.
Giuseppe

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Your line breaking settings in props.conf are wrong. We'll need to see some sample data to give the best settings.

---
If this reply helps you, Karma would be appreciated.
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!

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 ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...