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
Get Updates on the Splunk Community!

Splunk MCP & Agentic AI: Machine Data Without Limits

  Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization ...

Finding Based Detections General Availability

Overview  We’ve come a long way, folks, but here in Enterprise Security 8.4 I’m happy to announce Finding ...

Get Your Hands Dirty (and Your Shoes Comfy): The Splunk Experience

Hands-On Learning and Technical Seminars  Sometimes, you just need to see the code. For those looking for a ...